fix: add fields to version metadata for onboarding fix #4348
Conversation
This file contains 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
hkantare
reviewed
Feb 16, 2023
hkantare
reviewed
Feb 16, 2023
|
@hkantare please review again, this fix is urgent for a large customer and I would like to have it merged asap, thanks. |
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.
Some products will be onboarded with a modules section that was not previously supported by the terraform provider, adding the parameters to the version resource metadata fixes the issue.
There were more metadata fields added by the API than expected, these have all been added to the resources and data sources to support cm onboarding.
Also added
x_auth_tokento the docs for the cm version resource, and created thecm_validationdocs.