-
Notifications
You must be signed in to change notification settings - Fork 264
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
* Allow passwords and tokens to be sensitive Notification channels are configured by sending tokens and passwords via labels. This change allows the sensitive labels to be configured in a separate block so that they can be marked as Sensitive and hidden from plan output. Encoders and Decoders are used to manipulate the labels block before it is passed to the expanders/flatteners. The token can be specified in either place right now, but the intent is to remove the ability to manage these from being managed via the "labels" block in the next breaking change. * update description and remove old files * Add sensitive label example Signed-off-by: Modular Magician <magic-modules@google.com>
- Loading branch information
1 parent
7684052
commit ecba8cf
Showing
5 changed files
with
288 additions
and
88 deletions.
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,3 @@ | ||
```release-note:enhancement | ||
monitoring: Added `sensitive_labels` to `google_monitoring_notification_channel` so that labels like `password` and `auth_token` can be managed separately from the other labels and marked as sensitive. | ||
``` |
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
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
Oops, something went wrong.