crossplane / crossplane/uptest
CLI arg for hooks
- Dominant language
- Go
- Stars
- 28
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
Would be nice if we could set an CLI arg for each hook that annotates the value to all test resources
Example:
setting CLI arg
`--pre-assert-hook="myhook.sh"`
will assume the following annotation on all test resources:
`uptest.upbound.io/pre-assert-hook=myhook.sh`
Probably it makes sense to allow that the CLI arg can be overwritten by the hook annotation on a ressource
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the CLI argument parsing and hook annotation handling in the Go project. Trace how test resources receive hook annotations, then verify that each proposed CLI option annotates resources and that an explicit resource annotation takes precedence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100