query: extract config block before passing to the provider request #37637
+542
−227
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dsa0x
force-pushed
the
sams/xtract-config
branch
from
8393cca to
de4dce5
Compare
dsa0x
added
the
no-changelog-needed
dsa0x
force-pushed
the
sams/xtract-config
branch
from
de4dce5 to
df53161
Compare
dsa0x
added
the
1.14-backport
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Borrowing some idea from the config handling of actions.
The only need for the entire list block is so that we can evaluate the nested "config" block while having the full source information. After that, we can pass the only the cty.Value of the config block to the provider request. This limits the knowledge of the provider input configuration being just the "config" block to the resource node handlers.
Target Release
1.15.x
Rollback Plan
Changes to Security Controls
Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.
CHANGELOG entry