Hi Team,
some small additions to override the dafault XLD behaviour for devopsascode use-case.
Additional flexibility is useful especially in cases where the XLD is integrated in the existing CI/CD pipelines as the delivery tool and the XLD specific "cleverness" needs to be overriden, because of the existing pipeline logic.
Kindly introduce following improvements:
- force-override option for delivery, whereby the same deployment package kann be uploaded/overriden multiple times, Use-Case: delivery of the SNAPSHOTS under the same deployment package but with updated links to binary artefacts.
- force-undeploy option for deployment to pre-clean the infrastructure-nodes (override the default upgrade/merge logic) as we deliver the complete package
Kind Regards,
Yefym.
by: Yefym D. | about a year ago | Deployments
Comments
Regarding the option to forcefully override.
Currently, in XL CLI, we allow the overriding of deployment packages. This behavior differs from other application clients such as the API, UI, and older CLI.
We have received requests from other customers to prevent this behavior and standardize the behavior across all tools to prevent override from happening.
Are you performing the override through the UI or XL CLI?
Could you explain why your preferred way is the override behavior?
We could consider using a deployment property to determine whether overrides should be applied or not, either for the deployment itself or as a global setting for all deployments. What option would best meet the needs?
—
2. Regarding the option to forcefully undeploy.
When using the existing Undeploy option, what limitations have you noticed in your scenario?
In what scenarios would you choose to pre-clean the environment instead of using the merging logic?
Which types of infrastructure are you using? Is this specific to a particular infrastructure type in this case?