aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap
[Resource Type] - [BUG] - AutheticateOIDCConfig state becomes inconsistent
- Dominant language
- No language data
- Stars
- 1.1k
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
### Name of the resource
AWS::ElasticLoadBalancingV2::ListenerRule
### Resource Name
_No response_
### Issue Description
When updating AWS::ElasticLoadBalancingV2::ListenerRule AuthenticateOidcConfig parameters, it is possible to get into a situation where the value is not updated. This appears to be due to inconsistent state between the config and Cloudformation. Cloudformation can detect that a change is required (such as by changing the action ordering) and it will still keep old parameters in place. This could be related to when a Dynamic Reference is used for the parameter value.
### Expected Behavior
AWS::ElasticLoadBalancingV2::ListenerRule AuthenticateOidcConfig should always update when a template is updated or a Dynamic Reference is detected to have changed.
### Observed Behavior
Changing parameter values within a Dynamic Reference (such as within a Secret in Secrets Manager), updating the parameter value directly with a string or using a new target in the Dynamic Reference all did not change the value in the AWS::ElasticLoadBalancingV2::ListenerRule AuthenticateOidcConfig.
### Test Cases
Create AWS::ElasticLoadBalancingV2::ListenerRule AuthenticateOidcConfig with values configured as Dynamic References. Try to change the values.
### Other Details
_No response_
Contributor guide
Research direction
Start with the AWS::ElasticLoadBalancingV2::ListenerRule AuthenticateOidcConfig behavior described in the issue and reproduce it using Dynamic References. Test changes to Secrets Manager values, direct string parameters, and new Dynamic Reference targets; done means the configuration updates consistently when the template or referenced value changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100