Open markuman opened 2 years ago
Files identified in the description: None
If these files are inaccurate, please update the component name
section of the description or use the !component
bot command.
One other possibility rather than introduce a new control parameter might be to documentate any single option for the rules parameter ...
Summary
The current handling of rules might be resulting always in a changing task.
That depends on action types where boto3 is assuming default values when they are not requested (See https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/elbv2.html and search for
The default is
).For example, take action type
authenticate-oidc
User request
AWS response for describe rules
Module change detect
Note:
ClientSecret
andUseExistingClientSecret
are popped due postprocessing in that case, because AWS won't return none of them, but required one of them.changed
when not all defaults value a givenPoint
2.
is a very difficult one, because on the one hand, it is a bug. It can result in an unexpected change, e.g. when some properties were set to none-default values via cloudformation, terraform, cdk or even clicked. They got reset to defaults.But fixing it would also break backwards compatibility :) Because "use the defaults for all values that are not given" is the current behaviour.
I think a control parameter must be introduced, where you can say:
Issue Type
Bug Report
Component Name
elb_application_alb
Ansible Version
Collection Versions
AWS SDK versions
Configuration
OS / Environment
No response
Steps to Reproduce
see summary
Expected Results
see summary
Actual Results
Code of Conduct