handle renamed fields for resource identifiers #117
Merged
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.
The code that outputs Go code that sets
Spec
orStatus
fields to aresource identifier field was not accounting for cases where we renamed
the field. Such is the case for many of the RDS controller's resources,
since all the identifier fields for all resources are "de-stuttured" by
renaming, for example,
DBSubnetGroupName
to justName
orDBClusterParameterGroupName
to justName
.This patch simply ensures we account for renamed fields in the Spec and
Status during calls to
pkg/generate/code.SetResourceIdentifiers
andadds a unit test to ensure we don't regress in the future.
Issue aws-controllers-k8s/community#852
By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache 2.0 license.