Skip to content

feat: Remove force replacement from gcfs_config #8101

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

Conversation

modular-magician
Copy link
Collaborator

Gcfsconfig changes do not require to re-create node pools hence there is no point to ForceNew on each gcfsconfig change, gcfs can be enabled and disabled via GUI or gcloud CLI without recreating node pools, examples:
https://cloud.google.com/kubernetes-engine/docs/how-to/image-streaming#disable

https://cloud.google.com/kubernetes-engine/docs/how-to/image-streaming#enable_on_node_pools

Also, same issue noted here hashicorp/terraform-provider-google#18417

Release Note Template for Downstream PRs (will be copied)

container: removed unnecessary force replacement in `gcfs_config`

Derived from GoogleCloudPlatform/magic-modules#11553

[upstream:b3e10c032f80f42f5a53aab2f8c151cfcb465627]

Signed-off-by: Modular Magician <[email protected]>
@modular-magician modular-magician merged commit 104c276 into hashicorp:main Sep 4, 2024
4 checks passed
shuyama1 pushed a commit that referenced this pull request Sep 20, 2024
[upstream:b3e10c032f80f42f5a53aab2f8c151cfcb465627]

Signed-off-by: Modular Magician <[email protected]>
@modular-magician modular-magician deleted the downstream-pr-b3e10c032f80f42f5a53aab2f8c151cfcb465627 branch November 16, 2024 03:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant