Skip to content

fix: make workspace reset accept either --all or elements list#2137

Open
kotborealis wants to merge 1 commit into
apache:masterfrom
kotborealis:bst-reset-either
Open

fix: make workspace reset accept either --all or elements list#2137
kotborealis wants to merge 1 commit into
apache:masterfrom
kotborealis:bst-reset-either

Conversation

@kotborealis

Copy link
Copy Markdown
Contributor

When using bst workspace reset --all a.bst b.bst c.bst, list of elements is ignored and it resets all workspaces, which could be confusing.

This patch adds a check that either --all is specified or list of elementsis provided.

This also fixes the following strange problem:

Running bst workspace reset --all --soft (with en-dash in --soft) causes buildstream to parse it as: reset with all flag and with list of elements --soft, as it could not parse it as a flag due to en-dash. This leads to bst hard-resetting workspace when for user it seems like he requested the --soft-one.

Now bst would throw error that either --all or element list needs to be provided, and would not reset user changes to workspace.

Ref. #2136

When using `bst workspace reset --all a.bst b.bst c.bst`, list of
elements is ignored and it resets all workspaces, which could be
confusing.

This patch adds a check that either `--all` is specified or list
of elementsis provided.

This also fixes the following strange problem:

Running `bst workspace reset --all --soft` (with en-dash in `--soft`)
causes buildstream to parse it as: reset with `all` flag and with list
of elements `--soft`, as it could not parse it as a flag due to en-dash.
This leads to bst hard-resetting workspace when for user it seems like
he requested the `--soft`-one.

Now bst would throw error that either `--all` or element list needs to
be provided, and would not reset user changes to workspace.

Ref. apache#2136
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant