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
Please vote on this issue by adding a
👍 reaction to the original
issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra
noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Description
When using the provider to create Snowflake sinks, the private_key attribute within the configs block is sensitive, causing Terraform to treat the entire configs attribute as a sensitive value.
This makes it impossible to know what might actually be changing. For example, this plan included multiple changes to the buffer size and batch time, but we'd never know that because the whole configs key is sensitive and not viewable.
Terraform will perform the following actions:
# module.pulsar_snowflake_ingestion_telemetry_sink.pulsar_sink.sink will be updated in-place
~ resource "pulsar_sink" "sink" {
~ configs = (sensitive value)
id = "public/default/snowflake-ingestion-telemetry"
name = "snowflake-ingestion-telemetry"
# (18 unchanged attributes hidden)
# (1 unchanged block hidden)
If there was a way to display the whole config, but just mark the private key as sensitive that would be great.
New or Affected Resource(s)
pulsar_sinks
Potential Terraform Configuration
# Copy-paste your Terraform configurations here - for large Terraform configs,# please use a service like Dropbox and share a link to the ZIP file. For# security, you can also encrypt the files using our GPG public key.
References
#0000
The text was updated successfully, but these errors were encountered:
Community Note
👍 reaction to the original
issue to help the community and maintainers prioritize this request
noise for issue followers and do not help prioritize the request
Description
When using the provider to create Snowflake sinks, the private_key attribute within the configs block is sensitive, causing Terraform to treat the entire configs attribute as a sensitive value.
This makes it impossible to know what might actually be changing. For example, this plan included multiple changes to the buffer size and batch time, but we'd never know that because the whole configs key is sensitive and not viewable.
If there was a way to display the whole config, but just mark the private key as sensitive that would be great.
New or Affected Resource(s)
Potential Terraform Configuration
References
The text was updated successfully, but these errors were encountered: