fix(dev-env): vip dev-env info --all
should not ask for a slug
#1815
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR fixes the bug when
vip dev-env info --all
asks for a slug when more than one environment is available.Pull request checklist
New release checklist
Steps to Test
vip dev-env create -s test1 < /dev/null
vip dev-env create -s test2 < /dev/null
vip dev-env info --all
npm run build
,npm link
.vip dev-env info --all
should succeed now.