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

Incomplete import of Zero Trust entities #4475

Closed
3 tasks done
greatestfen opened this issue Oct 30, 2024 · 4 comments
Closed
3 tasks done

Incomplete import of Zero Trust entities #4475

greatestfen opened this issue Oct 30, 2024 · 4 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@greatestfen
Copy link

greatestfen commented Oct 30, 2024

Confirmation

  • This is a bug with an existing resource and is not a feature request or enhancement. Feature requests should be submitted with Cloudflare Support or your account team.
  • I have searched the issue tracker and my issue isn't already found.
  • I have replicated my issue using the latest version of the provider and it is still present.

Terraform and Cloudflare provider version

  • provider registry.terraform.io/cloudflare/cloudflare v4.44.0
    Your version of Terraform is out of date! The latest version
    is 1.9.8.

Affected resource(s)

  • cloudflare_zero_trust_device_profiles
  • cloudflare_zero_trust_tunnel_cloudflared
  • cloudflare_zero_trust_tunnel_cloudflared_config

Terraform configuration files

resource "cloudflare_zero_trust_tunnel_cloudflared" "tunnel" {
    name         = "tunnel"
    account_id   = var.cloudflare_account_id
###### it's importing with tunnel_token, changing to secret (as this is a required attribute) recreates resource
    secret       = jsondecode(data.aws_secretsmanager_secret_version.cloudflare_tunnel_token_version.secret_string)["TUNNEL_TOKEN"] 
    lifecycle {
        ignore_changes = [
            secret
        ]
    }
}

resource "cloudflare_zero_trust_tunnel_cloudflared_config" "tunnel_config" {
    account_id = var.cloudflare_account_id
    tunnel_id  = cloudflare_zero_trust_tunnel_cloudflared.tunnel.id

    config {
        warp_routing {
            enabled = true
        }
        ingress_rule {
            service = "https://10.0.0.3:8081"
        }
    }
#### missing required attribute 'ingress rule'
    lifecycle {
        ignore_changes = [
            config[0].ingress_rule
        ]
    }
}

resource "cloudflare_zero_trust_device_profiles" "default" {
    account_id            = var.cloudflare_account_id
    description           = "Default policy" #### required, but not being imported
    name                  = "default" #### required, but not being imported
    allow_mode_switch     = false
    allow_updates         = false
    allowed_to_leave      = true
    auto_connect          = 0
    captive_portal        = 180
    default               = true
    disable_auto_fallback = false
    enabled               = true
    exclude_office_ips    = false
    service_mode_v2_mode  = "warp"
    service_mode_v2_port  = 0
    switch_locked         = false
    precedence            = 1 #### required, but not being imported
}

Link to debug output

not needed

Panic output

No response

Expected output

No changes.

Actual output

cloudflare_zero_trust_device_profiles.default will be updated in-place

~ resource "cloudflare_zero_trust_device_profiles" "default" {
+ description = "Default policy"
id = "id"
+ name = "default"
+ precedence = 1
+ tunnel_protocol = "wireguard"

Steps to reproduce

terraform import cloudflare_zero_trust_device_profiles.default <account_id>/default
terraform import cloudflare_zero_trust_tunnel_cloudflared.tunnel <account_id>/<tunnel_id>
terraform import cloudflare_zero_trust_tunnel_cloudflared_config.tunnel_config <account_id>/<tunnel_id>

Additional factoids

No response

References

No response

@greatestfen greatestfen added kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Oct 30, 2024
Copy link
Contributor

Community Note

Voting for Prioritization

  • Please vote on this issue by adding a 👍 reaction to the original post 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.

Volunteering to Work on This Issue

  • If you are interested in working on this issue, please leave a comment.
  • If this would be your first contribution, please review the contribution guide.

Copy link
Contributor

Thank you for reporting this issue! For maintainers to dig into issues it is required that all issues include the entirety of TF_LOG=DEBUG output to be provided. The only parts that should be redacted are your user credentials in the X-Auth-Key, X-Auth-Email and Authorization HTTP headers. Details such as zone or account identifiers are not considered sensitive but can be redacted if you are very cautious. This log file provides additional context from Terraform, the provider and the Cloudflare API that helps in debugging issues. Without it, maintainers are very limited in what they can do and may hamper diagnosis efforts.

This issue has been marked with triage/needs-information and is unlikely to receive maintainer attention until the log file is provided making this a complete bug report.

@github-actions github-actions bot added triage/needs-information Indicates an issue needs more information in order to work on it. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Oct 30, 2024
Copy link
Contributor

Marking this issue as stale due to 30 days of inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 7 days it will automatically be closed. Maintainers can also remove the lifecycle/stale label.
If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

Copy link
Contributor

github-actions bot commented Dec 8, 2024

This issue was closed because it has been stalled for 7 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
None yet
Development

No branches or pull requests

1 participant