Follow-up from "Addition of --out option to bst artifact log" - allow artifact log overwriting
- Dominant language
- Python
- Stars
- 140
- Forks
- 45
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
[See original issue on GitLab](https://gitlab.com/BuildStream/buildstream/-/issues/1112)
In GitLab by [[Gitlab user @traveltissues]](https://gitlab.com/traveltissues) on Aug 29, 2019, 12:51
The following discussion from !1552 should be addressed:
- [ ] [[Gitlab user @traveltissues]](https://gitlab.com/traveltissues) started a [discussion](https://gitlab.com/BuildStream/buildstream/merge_requests/1552#note_209796891):
> I can imagine that this could happen a lot, maybe the better default behaviour is to overwrite logs?
Contributor guide
Research direction
Start with the original issue and the discussion on merge request !1552, then trace the `bst artifact log` command and its `--out` behavior. Confirm the intended overwrite semantics and update the relevant coverage so that existing artifact logs behave as agreed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100