Open florenp opened 11 months ago
Hello,
"The state show the enable_ipv4 = false but that's not the case in GCP Console. The instance also got a private ip but the attribute is not visible in terraform."
Partially, still have the issue related to public BUT ALSO missing private IP in terraform output. Even in the terraform state show whereas the instance has private IP in GCP HMI.
Hello @edwardmedia,
Yes that's the same issue. Didn't see it as it was closed, but closed without any fix.
We want to create a private CloudSQL with DMS Connection profile.
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 --version Terraform v1.6.4 on linux_amd64
Affected Resource(s)
google_database_migration_service_connection_profile
Terraform Configuration Files
Debug Output
Apply Step: https://gist.github.com/florenp/7f3672dfa1ad32fd5643e653bc9524bf
The state show the
enable_ipv4 = false
but that's not the case in GCP Console. The instance got only a public_ip instead of a private one. The instance also got a private ip but the attribute is not visible in terraform.Expected Behavior
CloudSQL Instance create by DMS should only a private ip.\
google_database_migration_service_connection_profile
should haveprivate_ip
attribute.Actual Behavior
CloudSQL Instance create by DMS got a public ip.\
google_database_migration_service_connection_profile
doesn't got anyprivate_ip
attribute.Steps to Reproduce
No special steps. Just plan/apply the change
b/313181869