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 me too comments, 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.
If an issue is assigned to a user, that user is claiming responsibility for the issue.
Customers working with a Google Technical Account Manager or Customer Engineer can ask them to reach out internally to expedite investigation and resolution of this issue.
The Cloud SDK documentation for the SSH tunnel states the private key is mutable. I'd like to propose google_datastream_connection_profile is updated-in-place when a private key is updated in forward_ssh_connectivity
Actual Behavior
Updating the private key in forward_ssh_connectivity forces a connection profile replacement. When a stream has a connection profile that is replaced it results in an unrecoverable failed stream.
This is an enhancement proposal since the current behavior is a force destroy and user would like that it be an update-in-place if the private_key argument is changed
Community Note
Terraform Version & Provider Version(s)
Terraform v1.7.0
on darwin_amd64
Affected Resource(s)
google_datastream_connection_profile
Terraform Configuration
Debug Output
No response
Expected Behavior
The
Cloud SDK
documentation for the SSH tunnel states the private key is mutable. I'd like to proposegoogle_datastream_connection_profile
is updated-in-place when a private key is updated inforward_ssh_connectivity
Actual Behavior
Updating the private key in
forward_ssh_connectivity
forces a connection profile replacement. When a stream has a connection profile that is replaced it results in an unrecoverable failed stream.Steps to reproduce
terraform plan
Important Factoids
No response
References
Connection-Profiles Cloud SDK
b/358666784
The text was updated successfully, but these errors were encountered: