-
Notifications
You must be signed in to change notification settings - Fork 343
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
CACHE-12946: add compatibility flag to override cache rules via cache… #3544
CACHE-12946: add compatibility flag to override cache rules via cache… #3544
Conversation
All contributors have signed the CLA ✍️ ✅ |
I have read the CLA Document and I hereby sign the CLA |
7dadfca
to
6d52401
Compare
recheck |
recheck |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please do not change existing flags, create a new number for your flag
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please do not change existing flags, create a new number for your flag
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please do not change existing flags, create a new number for your flag
0d0a0d4
to
9f920c1
Compare
9f920c1
to
6d52401
Compare
6d52401
to
f3c9248
Compare
sorry @danlapid fixed now, also can this please be approved and merged now? this PRs been sitting in the queue for almost 2 weeks now? |
@danlapid is there a way to run these workflows? I don't know status are they waiting for to be reported on ... |
Similar to #3342 adding a new compatibility flag to allow overriding cache rules via the request.cf object that can be specified on the
cache.put(Request)
API.Currently, if a resource is PUT via the cache API and have cache settings such as cacheEverything: true specified in the 'cf' object, while there is also cache rules defined against that resource, the cache settings in request cf object isn't respected. Cache team is working on fixing this behavior to give precedence over to request cf object first and then to cache rules, however, we are hiding this behavior behind a compatibility flag until we're confident the change works as intended for everyone.