test(pxe): pin constrained-kind AppTaggingSecret keys in tagging-store snapshots#24614
Merged
vezenovm merged 1 commit intoJul 9, 2026
Conversation
…e snapshots Add a CONSTRAINED-kind AppTaggingSecret to the Recipient and Sender tagging-store schema fixtures so the compatibility snapshots pin both the `constrained:` and `unconstrained:` key prefixes side by side. The constrained secret lands in all four persisted maps (recipient aged/finalized, sender pending/last-finalized).
mverzilli
approved these changes
Jul 9, 2026
vezenovm
merged commit 5fc0930
into
mv/f-680-migrate-pxe-tagging-stores
15 checks passed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on #24604.
Adds a
constrained-kindAppTaggingSecretto the Recipient and Sender tagging-store schema fixtures so the backwards-compatibility snapshots pin both theconstrained:andunconstrained:key prefixes side by side. Previously the fixtures only used default (unconstrained) secrets.The constrained secret lands in all four persisted maps (recipient aged/finalized, sender pending/last-finalized).