You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
If you create a public db (without private_network block), and after that, you change it to make it private by adding a private_network block, the DB keeps its public ip address in addition to obtaining its private ip.
Thank you for the report, It's gonna be fixed on the next release. You'll be enable to remove an ip handled by the IPAM service to a private subnet. e.g:
Community Note
Terraform Version
Terraform v1.5.3
terraform-provider-scaleway 2.24.0
Affected Resource(s)
Terraform Configuration Files
first instanciate a RDB without ip_net field
then, add ip_net configuration and apply the modification
The bug is also present if if you modify the CIDR in ip_net section on a private instance created with an ip_net value
Debug Output
Panic Output
Expected Behavior
The RDB is modified with the requested private IP endpoint (ex: 172.16.19.8:5432)
Actual Behavior
The RDB is modified with a public IP endpoint (ex: 195.154.196.110:24007)
Steps to Reproduce
terraform apply
Important Factoids
References
The text was updated successfully, but these errors were encountered: