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

Deprecation notice for cloudflare_access_application has the wrong replacement resource #4043

Closed
3 tasks done
komailo opened this issue Sep 17, 2024 · 2 comments · Fixed by #4044
Closed
3 tasks done
Labels
kind/bug Categorizes issue or PR as related to a bug. triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@komailo
Copy link
Contributor

komailo commented Sep 17, 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

Terraform v1.9.5
on linux_amd64
+ provider registry.terraform.io/cloudflare/cloudflare v4.41.0
+ provider registry.terraform.io/hashicorp/hcp v0.96.0

Affected resource(s)

  • cloudflare_access_application

Terraform configuration files

resource "cloudflare_access_application" "test" {
}

Link to debug output

N/A

Panic output

No response

Expected output

│ Warning: Deprecated Resource
│ 
│   with cloudflare_access_application.test,
│   on main.tf line 91, in resource "cloudflare_access_application" "test":
│   91: resource "cloudflare_access_application" "test" {
│ 
│ `cloudflare_access_application` is now deprecated and will be removed in the next major version. Use `cloudflare_zero_trust_access_application` instead.
│ 
│ (and 15 more similar warnings elsewhere)

The resource to use should be cloudflare_zero_trust_access_application vs currently its zero_trust_access_application which is not valid resource name.

Actual output

│ Warning: Deprecated Resource
│ 
│   with cloudflare_access_application.test,
│   on main.tf line 91, in resource "cloudflare_access_application" "test":
│   91: resource "cloudflare_access_application" "test" {
│ 
│ `cloudflare_access_application` is now deprecated and will be removed in the next major version. Use `zero_trust_access_application` instead.
│ 
│ (and 15 more similar warnings elsewhere)

Steps to reproduce

  1. Add the provided example
  2. run terraform plan
  3. see the deprecation notice

Additional factoids

No response

References

#3584

@komailo komailo 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 Sep 17, 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 Sep 17, 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. triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant