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

Enable the default route for cloudflare workers #2892

Closed
pksunkara opened this issue Oct 27, 2023 · 4 comments
Closed

Enable the default route for cloudflare workers #2892

pksunkara opened this issue Oct 27, 2023 · 4 comments
Labels
kind/enhancement Categorizes issue or PR as related to improving an existing feature. workflow/pending-public-documentation Indicates an issue or PR requires changes to public documentation confirming suitability for use. workflow/pending-upstream-library Indicates an issue or PR requires changes from an upstream library.

Comments

@pksunkara
Copy link

Current Terraform and Cloudflare provider version

Cloudflare provider: v4.4.0

Description

When I create a worker using cloudflare_worker_script, the default route created at {name}.{org}.workers.dev is not enabled.

And there's no way of enabling that default route in terraform.

Use cases

Would like to use that default route after enabling it. But there's no way of doing through terraform

Potential Terraform configuration

resource "cloudflare_worker_script" "my_script" {
  account_id = "f037e56e89293a057740de681ac9abbe"
  name       = "script_1"
  content    = file("script.js")
}

References

No response

@pksunkara pksunkara added kind/enhancement Categorizes issue or PR as related to improving an existing feature. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Oct 27, 2023
@pksunkara pksunkara changed the title Enable the default router for cloudflare workers Enable the default route for cloudflare workers Oct 27, 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.

@jacobbednarz jacobbednarz added workflow/pending-upstream-library Indicates an issue or PR requires changes from an upstream library. workflow/pending-public-documentation Indicates an issue or PR requires changes to public documentation confirming suitability for use. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Oct 27, 2023
@wsierakowski
Copy link

"cloudflare_worker_route" resource used to have property enabled which seems to be gone now:

resource "cloudflare_worker_route" "catch_all_route" {
  zone = "${var.zone}"
  pattern = "*${var.zone}/*"
  enabled = true
  depends_on = ["cloudflare_worker_script.main_script"]
}

There's no information in the docs how to create a route and enable it. Was this purposely removed due to some security concerns? The reason for removal of enabled property doesn't seem to be mentioned in the docs.

@jacobbednarz
Copy link
Member

This issue has been closed as we are now tracking this internally with service teams directly. If you would like an update or to be notified when/if the product ships with this change, please reach out to Cloudflare Support or your account team who can watch the internal feature request for you.

@pksunkara
Copy link
Author

This issue has been closed as we are now tracking this internally with service teams directly.

What do you mean? I thought this was a terraform issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement Categorizes issue or PR as related to improving an existing feature. workflow/pending-public-documentation Indicates an issue or PR requires changes to public documentation confirming suitability for use. workflow/pending-upstream-library Indicates an issue or PR requires changes from an upstream library.
Projects
None yet
Development

No branches or pull requests

3 participants