Skip to content

test(BA-7854): let the user policy seed carry a concurrent-login cap - #14547

Closed
jopemachine wants to merge 2 commits into
mainfrom
test/BA-7854-seed-user-policy-login-cap
Closed

test(BA-7854): let the user policy seed carry a concurrent-login cap#14547
jopemachine wants to merge 2 commits into
mainfrom
test/BA-7854-seed-user-policy-login-cap

Conversation

@jopemachine

Copy link
Copy Markdown
Member

Resolves BA-7854

Summary

  • SeedUserPolicy takes a max_concurrent_logins and says so in its detail. It is the only change to a shared scenario seed the resource policy scenarios need, so it goes in on its own.
  • The cap is the only value of a user policy an update may clear, so the row that clears it (BA-7853) needs a seeded policy holding one. The default stays None, so every row laid so far — and every existing report.md — reads the same.

Test plan

  • test-scenario on CI for every component that lays a user policy passes with its report.md unchanged

🤖 Generated with Claude Code

https://claude.ai/code/session_019vFCmtPMD6GLPBJxJoFroD

The cap is the one value of a user policy an update may clear, so a scenario
that clears it needs a seeded policy holding one. None is still the default,
so every row laid so far reads the same.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019vFCmtPMD6GLPBJxJoFroD
@github-actions github-actions Bot added the size:S 10~30 LoC label Sep 11, 2026
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019vFCmtPMD6GLPBJxJoFroD
@jopemachine

Copy link
Copy Markdown
Member Author

Not needed on its own: the seed change rides inside #14550, the one PR that uses it.

@jopemachine
jopemachine deleted the test/BA-7854-seed-user-policy-login-cap branch September 11, 2026 04:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:S 10~30 LoC

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant