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
Terraform Version
Terraform v1.9.8
Affected Resource(s)
scaleway_account_project
scaleway_instance_security_group
scaleway_instance_server
Terraform Configuration Files
# Copy-paste the minimal (if possible) terraform configuration to reproduce the bug here - for large Terraform configs,# please use a service like Dropbox and share a link to the ZIP file. For# security, you can also encrypt the files using our GPG public key: https://keybase.io/hashicorpprovider"scaleway" {
alias="tmp"
}
resourcescaleway_account_project"project" {
provider=scaleway.tmpname="my_project"
}
provider"scaleway" {
project_id=scaleway_account_project.project.id
}
resource"scaleway_instance_server""server" { // Will use scaleway_account_project.projectimage="ubuntu_jammy"type="PRO2-XXS"
}
When the apply command was executed, the "Default Security Group" resource was automatically created as part of the instance creation process. Therefore, the destroy command should have also deleted the "Default Security Group" resource.
Actual Behavior
The instance was successfully destroyed, but the "Default Security Group" was not. This omission ultimately prevented the complete destruction of the project.
Community Note
Terraform Version
Terraform v1.9.8
Affected Resource(s)
Terraform Configuration Files
Debug Output
https://gist.github.com/midnightpacket/c05136d107b5b74052c40b6324f60b2f
Panic Output
Expected Behavior
When the apply command was executed, the "Default Security Group" resource was automatically created as part of the instance creation process. Therefore, the destroy command should have also deleted the "Default Security Group" resource.
Actual Behavior
The instance was successfully destroyed, but the "Default Security Group" was not. This omission ultimately prevented the complete destruction of the project.
I used this doc as a reference https://registry.terraform.io/providers/scaleway/scaleway/latest/docs/resources/account_project#use-a-project-in-provider-configuration
Steps to Reproduce
terraform apply
terraform destroy
Important Factoids
References
The text was updated successfully, but these errors were encountered: