-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
default_version logic in google_ml_engine_model is broken #10432
Comments
@AndreasBergmeier6176 |
|
Result: There is This and no support for version in Terraform makes this basically unusable in Terraform. |
Hm, so the issue you are describing is that you have modified a field on this resource outside of Terraform and now Terraform is trying to reconcile that diff? You may want to look into a lifecycle directive to ignore changes on that field as you actively manage it outside of Terraform It's possible that we should not support the default_version field, but it would be a breaking change to do so at this point |
Thanks, that should do the trick for us. |
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
Terraform v1.0.1
on linux_amd64
Affected Resource(s)
Terraform Configuration Files
Expected Behavior
There should be no reference to version in model to begin with.
I expect that this design flaw comes directly from the backend.
With the current behavior I would even add a breaking change and remove
default_version
handling from Terraform entirely.Actual Behavior
After deploying a model version, the backend adds the following properties to ModelVersion:
And best of all changing
default_version
enforces replacement.Now there are various problems with this.
First off, should I reference a version, it basically creates a chicken/egg problem both for creation and destroying.
Second - currently there is not support for model versions in Terraform so you can only hardcode the value.
Third - adding a
default_version
at model creation time is not supported either.Steps to Reproduce
terraform apply
b/312911725
The text was updated successfully, but these errors were encountered: