Remove superseded Cloud Run simulation entry revisions
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 52/100
Research direction
Start by locating the deployment workflow for the simulation entry service and its Cloud Run promotion steps. Trace how production candidates become stable and where staging deployments diverge, then add focused automated tests for the cleanup conditions. Done means failed or unpromoted deployments leave revisions untouched, while a successful promotion retains only the active revision and removes older tags and revisions.
Written by the indexing model from the issue text.
Description
Problem
Each successful deployment of the simulation entry service creates a new Cloud Run revision, but the deployment workflow does not remove superseded revisions. These inactive revisions accumulate after subsequent production deployments.
Proposed change
- Run cleanup after a production candidate completes the deployment workflow and is promoted to stable traffic.
- Verify that the exact revision produced by the workflow is Ready and is the sole revision receiving 100% of service traffic.
- Remove traffic tags that reference older revisions.
- Delete every older revision while retaining the promoted revision.
- Skip cleanup for staging deployments that do not promote their candidate.
Acceptance criteria
- Failed or incomplete deployments cannot delete revisions.
- Unpromoted staging deployments do not run cleanup.
- A successful promoted deployment leaves only its active Cloud Run revision.
- The cleanup behavior has focused automated tests.
- Dominant language
- Python
- Stars
- 1
- Forks
- 1
- Avg merge
- 1d 32m
- Merged PRs (30d)
- 18
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from PolicyEngine/policyengine-sim-api
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
PolicyEngine/policyengine-sim-api#314 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
PolicyEngine/policyengine-sim-api#717 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
PolicyEngine/policyengine-sim-api#711 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
PolicyEngine/policyengine-sim-api#707 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
PolicyEngine/policyengine-sim-api#674 · 3 comments ·
Maintainers usually reply within 1 day
All issues in PolicyEngine/policyengine-sim-api
Similar issues
-
comp/tools duplicate P2 sweeper:risk-compatibility tool/mcp type/bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
NousResearch/hermes-agent#132042 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
deepset-ai/haystack#13092 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
EverMind-AI/Raven#845 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
AstrBotDevs/AstrBot#10340 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
BasedHardware/omi#20401 · 1 comment ·
Maintainers usually reply within 1 day