-
Notifications
You must be signed in to change notification settings - Fork 67
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
fix: fix datasource result blocks #763
Conversation
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.
Project Groups still needs updating.
Variables => Scope still has a List Nested Block, I think this might be intentional and part of the actual config but taking a look would be good.
@IsaacCalligeros95 I think when it comes to the datasource result set attributes, it probably doesn't matter. I think the resource schema types matter more |
docs/data-sources/variables.md
Outdated
@@ -37,24 +36,11 @@ data "octopusdeploy_variables" "example" { | |||
- `is_editable` (Boolean) Indicates whether or not this variable is considered editable. | |||
- `is_sensitive` (Boolean) Indicates whether or not this resource is considered sensitive and should be kept secret. | |||
- `prompt` (Attributes List) (see [below for nested schema](#nestedatt--prompt)) | |||
- `scope` (Attributes List) As variable names can appear more than once under different scopes, a VariableScope must also be provided (see [below for nested schema](#nestedatt--scope)) |
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.
Looking at the old schema docs it looks like the scope should be Required, sorry I think I mislead you on the last review.
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.
the scope is a nested property of the variable, within a datasource the results are all readonly, I think this feels right
|
||
- `description` (String) |
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 think these should still be Read only.
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.
A couple of minor comments.
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.
LGTM
related to #762