Skip to content
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

[datadog_synthetics_test] Add secure field to browser variables and update docs #1918

Merged
merged 11 commits into from
May 19, 2023
5 changes: 5 additions & 0 deletions datadog/resource_datadog_synthetics_test_.go
Original file line number Diff line number Diff line change
Expand Up @@ -1097,6 +1097,11 @@ func syntheticsBrowserVariableElem() *schema.Resource {
Required: true,
ValidateDiagFunc: validators.ValidateEnumValue(datadogV1.NewSyntheticsBrowserVariableTypeFromValue),
},
"secure": {
Description: "Determines whether or not the browser test variable is obfuscated.",
Type: schema.TypeString,
Optional: true,
},
},
}
}
Expand Down
4 changes: 2 additions & 2 deletions docs/resources/synthetics_test.md
Original file line number Diff line number Diff line change
Expand Up @@ -630,9 +630,9 @@ Required:
Optional:

- `example` (String) Example for the variable.
- `id` (String) ID of the global variable to use. This is actually only used (and required) in the case of using a variable of type `global`.
- `id` (String) ID of the global variable to use. This is actually only used (and required) in the case of using a variable of the `global` type.
- `pattern` (String) Pattern of the variable.

- `secure` (String) Determines whether or not the browser test variable is obfuscated.

<a id="nestedblock--config_variable"></a>
### Nested Schema for `config_variable`
Expand Down