Fix writing of aws_security_group name_prefix to statefile. #14475
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.
Community Note
Closes #14474
Release note for CHANGELOG:
Details
As reported in #14474, I've been seeing some of our security groups being recreated unnecessarily due to their name_prefix property not being written to the statefile.
resource.PrefixedUniqueId
generates names with a suffix containing hex digits, whereas the naming package was assuming these were purely decimal. This meant that NamePrefixFromName was returningnil
when the generated name included hex digits a-f, which in turn caused the name_prefix property not to be set in the statefile.