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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
team: add organization_access #155
team: add organization_access #155
Changes from 16 commits
8172d2f
1805d18
04b4665
6e22172
a846082
9e23381
4fa6aed
c651fe0
fa026d3
89090d4
c2e4f0c
e25915e
b2af973
35a720c
e4dccdf
21613fe
0c8263c
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm I'm not sure we want this to be marked as a computed value.
Computed
is used to represent values that are not user configurable or aren't known at time of anapply
orplan
operation, which this shouldn't be.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I set this based on the following comment from the plugin SDK:
I take that to mean that any with a server set default could be "computed," though this probably moot when it's an optional field where the zero value of the type is equal to the server value. If the server were capable of defaulting to
true
, I think this might need to be set though? I can remove it here.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, was mis-remembering what values
visibility
could have. I think this needs to be computed since the API will respond withvisibility = "secret"
regardless of whether the user has set a value and we'll persist that value to state. I would expect Terraform to present a diff from"secret" -> null
on subsequent runs if we don't account for this. I think computed takes care of this, but correct me if I'm wrong.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nope, the API should respond with whatever value the user set - and valid options are
"secret"
or"organization"
. The default is"secret"
.Computed
is very much for unknown values at plan-time that are not user-configurable - things like dates and UUIDs.Default
is for known values to be used when something isn't explicitly set within the configuration.For our case here, these are all values that have known defaults that we can provide at plan-time; so they can all be defaulted appropriately. (So this visibility section should not be computed, and should have a default of
"secret"
).When that's all finished, given a configuration like this:
We should see a plan output like this:
See the Schema Behaviors documentation for more info on both of these behaviors.