Skip to content

Conversation

@vkalapov
Copy link
Contributor

LMCROSSITXSADEPLOY-3367

Description:

Issue:

Yavor16
Yavor16 previously approved these changes Jan 16, 2026
LMCROSSITXSADEPLOY-3367
util.GetShortOption(taskExecutionTimeoutOpt): "Task execution timeout in seconds",
util.CombineFullAndShortParameters(startTimeoutOpt, timeoutOpt): "Start app timeout in seconds",
util.GetShortOption(shouldBackupPreviousVersionOpt): "(EXPERIMENTAL) (STRATEGY: BLUE-GREEN, INCREMENTAL-BLUE-GREEN) Backup previous version of applications, use new cli command \"rollback-mta\" to rollback to the previous version",
util.GetShortOption(dependencyAwareStopOrderOpt): "(STRATEGY: BLUE-GREEN, INCREMENTAL-BLUE-GREEN) Stop apps in a dependency-aware order during the resume phase of a blue-green deployment",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How is it guaranteed that this new flag is used only with the blue-green and incremental-blue-green strategies? Should we add validation for that and maybe a fallback for the other strategies when its wrongly used?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've tested with other strategy-specific parameters and the flag seems to be accepted and ignored for the operation that does not support it. In which case I think its ok to leave it without a strict failure for consistency.
I've moved the processBuilder call to deployment_strategy.go for better structural clarity and added relevant tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants