StackGuardian / StackGuardian/tirith
feat(platform): pass raw workflow parameters through `tirith platform check`
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 165
- Forks
- 42
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 11
Description
Status: on hold pending an internal product decision — do not build until unheld.
platform check builds the create-workflow/run payload itself; the user cannot supply connectors,
secrets, runner constraints, or any other run parameter the platform API accepts. Anyone needing a
cloud connector on the run is stuck.
Proposal (kept for when the hold lifts). Repeated --workflow-param key=value (dotted keys for
nesting) plus --workflow-payload params.json, deep-merged into the workflow/run body the CLI
constructs — CLI flags win over file, both win over defaults. Document which fields the CLI owns
(artifact paths, document kinds) and refuses to override. Secrets should also be readable from
stdin/env, matching the existing --api-key - convention, so they stay out of the process table.
Contributor 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.
Research direction
When the hold is lifted, start at the tirith platform check entry point and review the existing --api-key - handling. Confirm parameter precedence, protected CLI-owned fields, and stdin/env secret behavior against the platform payload; done means the documented flags and JSON input are accepted without overriding those fields.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100