fix: Correct key used on license_configuration_arn
#2796
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.
Description
Following issue #2753.
Motivation and Context
Currently, it is not possible to provide a license through the
self-managed-node-group
andeks-managed-node-group
modules.This is necessary in cases like the following configuration:
Breaking Changes
I do not see any potential breaking changes.
How Has This Been Tested?
examples/*
to demonstrate and validate my change(s)examples/*
projectspre-commit run -a
on my pull requestAfter these modifications, I can define
license_configuration_arn
as follows:I'm not entirely sure in this case if it makes sense to have the map within a list. If you have a better idea, please feel free to suggest it. Nevertheless, it's currently working well for me in this way.