Skip to content

Update how operations use backend config state in context of PSS #37248

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

Draft
wants to merge 5 commits into
base: pss/store-pss-in-planfile
Choose a base branch
from

Conversation

SarahFrench
Copy link
Member

Follow up to #37246

Target Release

N/A

Rollback Plan

  • If a change needs to be reverted, we will roll out an update to the code within 7 days.

Changes to Security Controls

Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.

CHANGELOG entry

  • This change is user-facing and I added a changelog entry.
  • This change is not user-facing.

@SarahFrench SarahFrench added the no-changelog-needed Add this to your PR if the change does not require a changelog entry label Jun 17, 2025
@SarahFrench SarahFrench changed the title Pss/update how operations use backend config state Update how operations use backend config state in context of PSS Jun 17, 2025
Copy link
Contributor

The equivalence tests failed. Please investigate here.

@SarahFrench SarahFrench changed the base branch from main to pss/store-pss-in-planfile June 17, 2025 18:49
Copy link
Contributor

The equivalence tests failed. Please investigate here.

@SarahFrench SarahFrench force-pushed the pss/store-pss-in-planfile branch from 7b80adb to a2acc33 Compare June 18, 2025 09:00
@SarahFrench SarahFrench force-pushed the pss/update-how-operations-use-backend-config-state branch from 1da8373 to cd0c5b2 Compare June 18, 2025 09:03
Copy link
Contributor

The equivalence tests failed. Please investigate here.

@SarahFrench SarahFrench force-pushed the pss/update-how-operations-use-backend-config-state branch from 2415a6f to a5a439f Compare June 18, 2025 11:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-changelog-needed Add this to your PR if the change does not require a changelog entry
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant