fix(secure-onboarding) Fix resource update operation #435
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 TF provider’s knowledge of cloud account object is older and different from the actual BE cloud account. This is because BE has modified the account object with fields like
organization_id
during org onboarding. Hence, during intended PUTs, TF overwrites these fields resulting in unexpected state.Fix summary:
organization_id
in provider's account resource schema (as acomputed
field only). This is to let the customers know if their onboarded account is part of any org when they fetch the real existing infrastructure objects using GET calls.Testing done:
Validated the scenarios :-
organization_id
on the account.organization_id
to""