-
Notifications
You must be signed in to change notification settings - Fork 57
Description
Describe the bug
In specific cases it is required to leverage a type: ods
but configure replica=0.
A common example is a repository of AWS lambda code.
To Reproduce
Steps to reproduce the behavior:
- Create repository of type:ods
- add openshift\template.yaml to that repo (having
replicas: 0
) - Deploy to D
- Open file
openshift\ods-deployments.json
and verify containers sha of given image)
Expected behavior
File openshift\ods-deployments.json
should include image tag in form of @sha256:....
instead of :latest
.
Affected version (please complete the following information):
- OpenShift: 4.x
- OpenDevStack 4.x
Log Output (ensure to remove any confidential information like tokens, project names, etc.
n/a
Additional context
Input for file openshift\ods-deployments.json
is derived from function getPodDataForDeployments. If a pod is not started that data is not properly updated.
ods-jenkins-shared-library/src/org/ods/orchestration/util/MROPipelineUtil.groovy
Lines 589 to 592 in bf555a7
deployments = os.getPodDataForDeployments( | |
project.targetProject, | |
OpenShiftService.DEPLOYMENTCONFIG_KIND, | |
deploymentDescriptor.deploymentNames |
Currently the types are very limited to specific ODS deployments, however the framework might be used in multiple dimensions.