provider/aws: Reworked validateArn function to handle empty values #10833
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.
Context
This is a proposal to fix #10806.
Chronologically, #10356 enforced that kms_key* attributes should be ARNs.
Then, hashicorp/hil#38 added the support for comparison and boolean operations.
Since then, resources were way more flexible and we could set attributes depending on other ones (for instance the env/stack).
As it is not possible to pass null values in resource arguments, the validateArn function is called against an empty value (
""
) and then returning errors.Having this empty argument is allowed, as the code is taking care of getting the value if set/changed.
Work
This work adds a
validateArnIfSet
method, allowing parameters with empty values.It is just a simple function checking if the value is empty, and running validateArn internally if not.
Tests
If needed, I can add per-resource tests, checking for the parameter validation/emptyness.