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

cloudamqp_vpc import does not import subnet #315

Open
ricardochaves opened this issue Feb 10, 2025 · 4 comments
Open

cloudamqp_vpc import does not import subnet #315

ricardochaves opened this issue Feb 10, 2025 · 4 comments
Labels
api or backend Needs to be addressed in the API backend

Comments

@ricardochaves
Copy link

I have a VPC connected with Azure running em production.
I'm trying to bring this configuration to terraform.
When I import it, my subnet becomes null

> terraform state show my_vpc_imported_state

resource "cloudamqp_vpc" "azure_vpc" {
    id       = "999999"
    name     = "testing"
    region   = "azure-arm::westus2"
    subnet   = null
    tags     = []
    vpc_name = "vpc_fake_name"
}

This is different than when I create a VPC from scratch:

resource "cloudamqp_vpc" "azure_vpc" {
    id       = "999999"
    name     = "testing"
    region   = "azure-arm::westus2"
    subnet   = "10.56.72.0/24"
    tags     = []
    vpc_name = "vpc_fake_name"
}

After the import, every time I make a plan it understands that the subnet has changed and tries to recreate the VPC

Am I doing something wrong?

@ricardochaves
Copy link
Author

I did some new tests.
I changed the file and state manually, but when I did a refresh it puts null in the subnet again.
This ended up blocking me. I can't use the import, I'll only be able to continue if I have to destroy and recreate the VPC, this is a problem for me.

@dentarg
Copy link
Member

dentarg commented Feb 11, 2025

@ricardochaves can you email our support and share debug logs or the actual name of the VPC you are trying to import?

@ricardochaves
Copy link
Author

I sent the email. I didn't receive any automatic response with a ticket number.

I included your name in the ticket, if you could take a look, I would appreciate it.

@dentarg dentarg added the api or backend Needs to be addressed in the API backend label Feb 11, 2025
@dentarg
Copy link
Member

dentarg commented Feb 11, 2025

Thanks, @tbroden84 took a look and there are some backend inconsistencies we need to work out. We will reply here and in the ticket when we have news to share.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api or backend Needs to be addressed in the API backend
Projects
None yet
Development

No branches or pull requests

2 participants