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

Exposing the VPC ID on the qovery_cluster resource? #378

Open
jpetitcolas opened this issue May 10, 2024 · 0 comments
Open

Exposing the VPC ID on the qovery_cluster resource? #378

jpetitcolas opened this issue May 10, 2024 · 0 comments

Comments

@jpetitcolas
Copy link

Hey team!

Would it be possible to expose the VPC ID of the qovery_cluster resource? That would be great to ease the peering with other VPCs.

I checked with a terraform state show, but I didn't find it in the cluster:

resource "qovery_cluster" "cluster" {
    advanced_settings_json = jsonencode(
        {
            "aws.eks.ec2.metadata_imds"         = "optional"
            "database.mysql.allowed_cidrs"      = ["REDACTED"]
            "database.postgresql.allowed_cidrs" = ["REDACTED"]
            "loki.log_retention_in_week"        = 60
        }
    )
    cloud_provider         = "AWS"
    credentials_id         = "[REDACTED]"
    disk_size              = 100
    features               = {
        static_ip  = false
        vpc_subnet = "[REDACTED]"
    }
    id                     = "[REDACTED]"
    instance_type          = "t3.xlarge"
    kubernetes_mode        = "MANAGED"
    max_running_nodes      = 8
    min_running_nodes      = 4
    name                   = "[REDACTED]"
    organization_id        = "[REDACTED]"
    region                 = "us-east-1"
    routing_table          = [
        # (1 unchanged element hidden)
    ]
    state                  = "DEPLOYED"
}

Not a big blocker: we can still use a variable to store the VPC ID retrieved from the AWS console.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant