[PL-42246] : Added more information in docs to have better clarity #766
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
adiyaar24
changed the title
adiyaar24
requested review from
VikasMaddukuriHarness,
tiwaritejas and
Jimit09Gandhi
VikasMaddukuriHarness
previously approved these changes
Nov 20, 2023
Jimit09Gandhi
previously requested changes
Nov 20, 2023
brian-f-harness
previously approved these changes
Nov 20, 2023
Co-authored-by: brian-f-harness <brian.fisher@harness.io>
adiyaar24
dismissed stale reviews from brian-f-harness and VikasMaddukuriHarness
via
4546adc
Co-authored-by: brian-f-harness <brian.fisher@harness.io>
sahibaHarness
approved these changes
Nov 21, 2023
VikasMaddukuriHarness
approved these changes
Nov 21, 2023
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.
Describe your changes
When setting up a new resource group using Terraform, if a user neglects to specify the included scopes, the backend (BE) takes charge by automatically populating the default scope.
However, during subsequent changes, Terraform attempts to make the scope null, assuming it was never defined by the user. The snag arises because the backend doesn't permit this operation; the scope is a required field in our database. To enhance clarity, we're updating our documentation to ensure a more transparent understanding of these intricacies.
Comment Triggers
PR Check triggers
trigger buildtrigger subcategoryfieldchecktrigger gitleaks