-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Service Account change in google_bigquery_data_transfer_config forces replacement #14123
Comments
Looks like it could take below
|
@giulianobr , can you please provide the config if possible? Thanks. |
Hi, I'm using a simple one, like this:
For testing purpose, try to create it without the service_account_name, apply the code, then include it again and apply it. You will see Terraform will force-replace the resource, instead of, in place modification. |
It looks like setting the update_mask accordingly for a url_param_only is currently not supported in magic-modules and needs a workaround. |
So, there's a way to solve it ? @zli82016 and @edwardmedia |
Unfortunately, I do not find a way to solve it. |
Note: Looks harder than |
b/280337862 |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Community Note
modular-magician
user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned tohashibot
, a community member has claimed the issue already.Terraform Version
1.4.2
Affected Resource(s)
Google Provider version
4.59
Terraform Configuration Files
In the resource "google_bigquery_data_transfer_config" if you change the service_account_name after you already applied your tf plan, the new apply will force replace the Scheduled Query.
Why is this happening, if we can replace the service account in a scheduled query using the following cmd:
Thanks,
The text was updated successfully, but these errors were encountered: