You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[feat][gov] Update repo to reflect v.2.9.0 of the API (#52)
* update repo to reflect v.2.9.0 of the api
* fixes to cursor slop
* notes in readme
* all tests passing, working on a local server with real examples
* docs
* lint fixes
* add comment on folder deletion recursion
* notes on reviewing
* better handling for config variables as secret
* update docs
* lint
* lint
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -66,3 +66,13 @@ New version should show up on Terraform Repository in 10-15 minutes.
66
66
# Update Retool CLI
67
67
Retool CLI has a `terraform` command that generates Terraform configuration from existing Retool org: https://github.com/tryretool/retool-cli/blob/master/src/commands/terraform.ts.
68
68
If you added a new resource or updated an existing one, you should update Retool CLI as well, so that your changes are reflected in auto-generated configuration.
69
+
70
+
# Reviewing
71
+
72
+
Reviewing PRs to this repo can be a challenge, particularly when they impact the OpenAPI generated code for the SDK.
73
+
74
+
As a general rule, code within `internal/provider/sdk` will be generated, and can largely be ignored during reviews.
75
+
76
+
Code _outside_ of this should be given close attention. `internal/provider` code is what drives the terraform behavior, and should be reviewed for correctness and backward compatibility. Tests should accompany new features, and reviewers should make a habit of checking out PR branches and running them against realisitic example retool deployments.
77
+
78
+
Updates should always include documentation updates for new/changed behaviors.
-`description` (String) A brief description of the configuration variable's purpose.
71
+
-`secret` (Boolean) Whether the configuration variable is a secret. Secrets are encrypted and not exposed in the Retool UI.
71
72
72
73
### Read-Only
73
74
74
75
-`id` (String) The unique identifier for the configuration variable.
75
-
-`secret` (Boolean) Whether the configuration variable is a secret. Secrets are encrypted and not exposed in the Retool UI. Secert is currently not supported as the values are encrypted and cannot be retrieved via the API.
76
76
77
77
<aid="nestedatt--values"></a>
78
78
### Nested Schema for `values`
79
79
80
80
Required:
81
81
82
82
-`environment_id` (String) The ID of the environment this value is associated with.
83
-
-`value` (String) The value of the configuration variable for the specified environment.
83
+
-`value` (String, Sensitive) The value of the configuration variable for the specified environment.
-`account_details_access` (Boolean) Whether the group has access to account details.
40
41
-`audit_log_access` (Boolean) Whether the group has access to the audit log.
41
42
-`landing_page_app_id` (String) The app ID of the landing page.
43
+
-`theme_access` (Boolean) Whether the group has access to edit themes.
42
44
-`universal_app_access` (String) The universal app access level for the group. This denotes the access level that this group has for all apps. Accepted values: none|use|edit|own
43
45
-`universal_query_library_access` (String) Level of access that the group has to the Query Library. Accepted values: none|use|edit
44
46
-`universal_resource_access` (String) The universal resource access level for the group. This denotes the access level that this group has for all resources. Accepted values: none|use|edit|own
-`auto_branch_naming_enabled` (Boolean) When enabled, Retool automatically suggests a branch name on branch creation. Defaults to true.
30
+
-`auto_cleanup_branches_enabled` (Boolean) When enabled, Retool automatically cleans up branches after they are merged. Defaults to false.
29
31
-`custom_pull_request_template` (String) Pull requests created from Retool will use the template specified.
30
32
-`custom_pull_request_template_enabled` (Boolean) When enabled, Retool will use the template specified to create pull requests. Defaults to false.
31
33
-`force_uuid_mapping` (Boolean) When set to true, creates a uuid mapping for protected elements to be used in the source control repo. Defaults to false.
0 commit comments