We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe Feature When trying to select the type of automatic rollback by default it uses "DEPLOYMENT_FAILURE"
the suggested change is to change the value from string to list(string) to be able to use both options to cover those edge cases cover
able to select both options for automatic rollback
cover edge cases in which applications are healthy but throwing multiples errors
variable "auto_rollback_configuration_events" { type = list(string) default = "DEPLOYMENT_FAILURE" description = "The event type or types that trigger a rollback. Supported types are `DEPLOYMENT_FAILURE` and `DEPLOYMENT_STOP_ON_ALARM`." } dynamic "auto_rollback_configuration" { for_each = local.auto_rollback_configuration_enabled ? [1] : [0] content { enabled = local.auto_rollback_configuration_enabled events = var.auto_rollback_configuration_events } }
allowing use both options for automatic rollback
I think will make more dynamic the use of the module to cover edge cases
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the Feature
Describe Feature
When trying to select the type of automatic rollback by default it uses "DEPLOYMENT_FAILURE"
the suggested change is to change the value from string to list(string) to be able to use both options to cover those edge cases cover
Expected Behavior
able to select both options for automatic rollback
Use Case
cover edge cases in which applications are healthy but throwing multiples errors
Describe Ideal Solution
allowing use both options for automatic rollback
Additional Context
I think will make more dynamic the use of the module to cover edge cases
The text was updated successfully, but these errors were encountered: