[datadog_synthetics_test] Add secure field to synthetics config variable #1696
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
skarimo
reviewed
Jan 3, 2023
kayayarai
previously approved these changes
Jan 3, 2023
Co-authored-by: skarimo <[email protected]> Co-authored-by: Kari Halsted <[email protected]>
…_local_var_secure_field
skarimo
approved these changes
Jan 4, 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.
SSIA, resolves #1585
Note - since the backend no longer returns the
securevariable, settingsecure = truewill result in drift if the variable pattern/example are updated elsewhere (via curl, API client, or web app).