docs: --set/--del are not available on every create/update
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 73/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- go
- Domain
- cli, documentation
Research direction
Read docs/claude-skill.md, cmd/harness/noargs.txt, and docs/mutation.md, then compare their create/update guidance with harness update pipeline --help. Scope --set/--del to nouns that support them and state when to use -f; done when the documentation matches the available command options.
Written by the indexing model from the issue text.
Description
docs/claude-skill.md (lines 23-24, 85) and the root help (cmd/harness/noargs.txt) say create takes -f or --set key=value, and update takes --set/--del or -f. That only holds for nouns that declare mutable fields.
harness update pipeline --help # only -f/--file, no --set/--del
Fix: scope the --set/--del statement to nouns that support it (check harness update <noun> --help; see docs/mutation.md) and fall back to -f. Alternatively, add --set to update pipeline.
Split out of #369 (item 5).
- Dominant language
- Go
- Stars
- 28
- Forks
- 16
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 65
Getting set up
- No Dockerfile or Docker Compose file
- No 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 harness/cli
-
docs: flags and behaviour in Command Reference/FAQ/claude-skill don't match the binary (-y, --since, --yaml, envelope, --set, kg)Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Maintainers usually reply within 2 days
Similar issues
-
Type: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
projectdiscovery/notify#569 ·
-
internal
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Results from sources can contain invalid host namesPossibly taken @Mzack9999 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
projectdiscovery/subfinder#1983 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
bug triaged
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
radius-project/radius#13566 · 2 comments ·
Maintainers usually reply within 1 day