-
Notifications
You must be signed in to change notification settings - Fork 209
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
fix: When setting a new zcfBundleCap, store it in baggage #8807
Conversation
b6cc93e
to
e9e2da6
Compare
f200054
to
392fd33
Compare
392fd33
to
b33d568
Compare
e9e2da6
to
26f2999
Compare
@Chris-Hibbert it looks like the |
That's definitely either an oversight or just a bad merge. Those changes should be included here. |
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.
Some changes are missing in the rebase.
Thanks for catching this. I added the missing commit. |
refs: #8806
Description
Copy of #8806 for the upgrade-15 release branch
Security Considerations
None
Scaling Considerations
None
Documentation Considerations
None
Testing Considerations
As we're testing zoe upgrades in a3p, verify that the newly set value survives zoe upgrade.
Upgrade Considerations
Prep it for upgrade.