Skip to content
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

Cloud SQL EnableGoogleMlIntegration is not working #3000

Open
kaiwen789 opened this issue Feb 19, 2025 · 1 comment
Open

Cloud SQL EnableGoogleMlIntegration is not working #3000

kaiwen789 opened this issue Feb 19, 2025 · 1 comment
Labels
awaiting-upstream The issue cannot be resolved without action in another repository (may be owned by Pulumi). kind/bug Some behavior is incorrect or out of spec

Comments

@kaiwen789
Copy link

kaiwen789 commented Feb 19, 2025

Describe what happened

We have a problem turning on the flag EnableGoogleMlIntegration in a Cloud SQL instance with Pulumi's Golang SDK.

We have confirmed that the configuration (PG16, custom-1-3840) is supported.
Likely it's similar to hashicorp/terraform-provider-google#17819.

Sample program

inst, err := sql.NewDatabaseInstance(ctx, instanceName, &sql.DatabaseInstanceArgs{
  Name:            pulumi.String("<redacted>"),
  DatabaseVersion: pulumi.String("POSTGRES_16"),
  Region:          pulumi.String("<redacted>"),
  InstanceType:    pulumi.String("CLOUD_SQL_INSTANCE"),
  Project:         pulumi.String("<redacted>"),
  Settings: &sql.DatabaseInstanceSettingsArgs{
  	DeletionProtectionEnabled: pulumi.Bool(false),
  	Tier:                      pulumi.String("db-custom-1-3840"),
  	AvailabilityType:          pulumi.String("ZONAL"),
  	BackupConfiguration: &sql.DatabaseInstanceSettingsBackupConfigurationArgs{
  		Enabled:                    pulumi.Bool(false),
  		PointInTimeRecoveryEnabled: pulumi.Bool(false),
  	},
  	MaintenanceWindow: &sql.DatabaseInstanceSettingsMaintenanceWindowArgs{
  		Day:         pulumi.Int(6),
  		Hour:        pulumi.Int(7),
  		UpdateTrack: pulumi.String("canary"),
  	},
  	DatabaseFlags: &sql.DatabaseInstanceSettingsDatabaseFlagArray{
  		&sql.DatabaseInstanceSettingsDatabaseFlagArgs{
  			Name:  pulumi.String("max_connections"),
  			Value: pulumi.String("500"),
  		},
  		&sql.DatabaseInstanceSettingsDatabaseFlagArgs{
  			Name:  pulumi.String("cloudsql.iam_authentication"),
  			Value: pulumi.String("on"),
  		},
  		&sql.DatabaseInstanceSettingsDatabaseFlagArgs{
  			Name:  pulumi.String("google_ml_integration.enable_model_support"),
  			Value: pulumi.String("on"),
  		},
  		&sql.DatabaseInstanceSettingsDatabaseFlagArgs{
  			Name:  pulumi.String("cloudsql.enable_google_ml_integration"),
  			Value: pulumi.String("on"),
  		},
  	},
  	EnableGoogleMlIntegration: pulumi.Bool(true),
  },
  })

Log output

No response

Affected Resource(s)

No response

Output of pulumi about

* Error, failed to update instance settings for : googleapi: Error 400: Invalid request: Google ML integration is not yet supported for this instance. Please set enable_google_ml_integration to false.., invalid

Additional context

No response

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

@kaiwen789 kaiwen789 added kind/bug Some behavior is incorrect or out of spec needs-triage Needs attention from the triage team labels Feb 19, 2025
@t0yv0
Copy link
Member

t0yv0 commented Feb 21, 2025

Thanks for reporting this @kaiwen789 ! Indeed at a first glance Pulumi provider is not doing anything special for this resource, in which case I suspect this issue should reproduce in Terraform as well. It appears the hashicorp/terraform-provider-google#17819 got closed and presumably fixed, but perhaps the particular variation you are hitting would still reproduce in Terraform. If that is the case it would be extremely helpful to open a new issue against hashicorp/terraform-provider-google - and link here - the ideal fix for this in Pulumi is having it fixed upstream and inheriting the fix through a regular update. Thank you.

@t0yv0 t0yv0 added awaiting-upstream The issue cannot be resolved without action in another repository (may be owned by Pulumi). and removed needs-triage Needs attention from the triage team labels Feb 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting-upstream The issue cannot be resolved without action in another repository (may be owned by Pulumi). kind/bug Some behavior is incorrect or out of spec
Projects
None yet
Development

No branches or pull requests

2 participants