-
Notifications
You must be signed in to change notification settings - Fork 0
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
Ability to purge cache for a URL #1
Labels
enhancement
New feature or request
Comments
You want a CLI command to purge a specific url instead of the whole host? |
Eventually a customer facing api.
I can use the cf interface today (which is what I used this evening).
But cli FTW as well👍
…On Fri, Sep 3 2021 at 9:02 PM, Randy Lebeau < ***@***.*** > wrote:
You want a CLI command to purge a specific url instead of the whole host?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub (
#1 (comment) ) , or unsubscribe
(
https://github.com/notifications/unsubscribe-auth/AE6P44S7F74NL27NNPRSR7TUAGK4HANCNFSM5DM2F2DA
).
|
We should work the customer facing api into the development schedule along with a portal sprint. Prioritize it against new features. I can def add it to the CLI on Monday. |
👍
…On Fri, Sep 3 2021 at 9:06 PM, Randy Lebeau < ***@***.*** > wrote:
We should work the customer facing api into the development schedule along
with a portal push. Prioritize it against new features. I can def add it
to the CLI on Monday.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub (
#1 (comment) ) , or unsubscribe
(
https://github.com/notifications/unsubscribe-auth/AE6P44UBBDIHOXZGFDEMOBDUAGLNHANCNFSM5DM2F2DA
).
|
The core of this is done. Just needs to be added to the CLI and portal. In the mean time it can be cleared via the cloudflare portal via Cache Tag. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe:
In an instance where a particular page is pushed live, but has a bad piece of code - we may need to purge just that page (and not wait the 15m maximum period).
Describe the solution you'd like:
Add Purge URL to API endpoint
Describe alternatives you've considered:
Wiating up to 15m with a busted page.
Additional context:
I think this can be exposed as a proxied Endpoint to the purge by URL (which worked in this case we had today)
The text was updated successfully, but these errors were encountered: