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

Import not working for cloudflare access application #2855

Closed
2 tasks done
kdmenghani13 opened this issue Oct 17, 2023 · 4 comments
Closed
2 tasks done

Import not working for cloudflare access application #2855

kdmenghani13 opened this issue Oct 17, 2023 · 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

@kdmenghani13
Copy link

Confirmation

  • My issue isn't already found on the issue tracker.
  • I have replicated my issue using the latest version of the provider and it is still present.

Terraform and Cloudflare provider version

Terraform - 1.5.5
Cloudflare - 4.16.0

Affected resource(s)

Cloudflare access application

Terraform configuration files

resource "cloudflare_access_application" "accessApplication" {
  provider                  = cloudflare.cf
  zone_id                   = <zoneid>
  name                      = "testing app"
  domain                    = "test.example.com"
  session_duration          = "24h"
  auto_redirect_to_identity = true
  http_only_cookie_attribute = true
  same_site_cookie_attribute = "strict"
  allowed_idps              = ["<enterprise common IDP>"] 
}

Link to debug output

╷ │ Error: failed to read Access Application state │ │

Panic output

No response

Expected output

Terraform import should be able to import the resource in state file.

Actual output

It fails with the below error.
Error: failed to read Access Application state

Steps to reproduce

I have the sample code from the docs, then ran the below import command. However it still fails to import the resource.
Step 1. code in main.tf
resource "cloudflare_access_application" "accessApplication" {
provider = cloudflare.cf
zone_id =
name = "testing app"
domain = "test.example.com"
session_duration = "24h"
auto_redirect_to_identity = true
http_only_cookie_attribute = true
same_site_cookie_attribute = "strict"
allowed_idps = [""]
}

Step 2. Terraform import command
terraform import cloudflare_access_application.accessApplication <account_id>/<application_id>

Additional factoids

No response

References

No response

@kdmenghani13 kdmenghani13 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 17, 2023
@github-actions
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.

@github-actions
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 17, 2023
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

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 Nov 25, 2023
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