fix(aws_elasticache_user): ignore noop changes with no-password auth #42712
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Rollback Plan
If a change needs to be reverted, we will publish an updated version of the library.
Changes to Security Controls
There are no changes to security controls.
Description
This is my first PR in this repo, I read the contribution guidelines but please let me know if I forgot something :) .
As reported in #33877 this provider always reports a difference when using ElastiCache Users with the authentication type
no-password-required
.AWS accepts this input value but returns
no-password
as output type which causes a diff that is always reconciled but effectively a no-op.Some users ignore the
authentication_mode
field as a workaround as described in the referenced issue.I checked the docs and related resources where I also found the option to use the
CustomizeDiff
function but decided to useDiffSuppressFunc
as it is used for similar changes - let me know if you prefer something else.Thanks for having a look!
Relations
Closes #33877
References
Output from Acceptance Testing
I added a new test for the no password authentication mode with the following output before I added my fix:
After adding my fix all tests finished successfully: