-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add vip dev-env purge command logic #1537
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sjinks
force-pushed
the
trunk
branch
2 times, most recently
from
November 7, 2023 08:40
ce8ac7d
to
50cb74a
Compare
rebeccahum
force-pushed
the
feature/devenv-purge-cmd
branch
2 times, most recently
from
November 22, 2023 00:05
18a1a8e
to
44493f9
Compare
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
rebeccahum
force-pushed
the
feature/devenv-purge-cmd
branch
4 times, most recently
from
November 22, 2023 15:59
883e94b
to
f8643a7
Compare
The linting errors due to spaces were auto fixed nicely. I think the errors with the await statements might need more thought. I frankenstien'd `vip-dev-env-list` with `vip-dev-env-delete`. My rationale was to send the delete command, wait for its success, then send the next one. The linter doesn't like this loop though.
rebeccahum
force-pushed
the
feature/devenv-purge-cmd
branch
from
November 22, 2023 21:30
f8643a7
to
3698a7f
Compare
sjinks
reviewed
Nov 22, 2023
sjinks
reviewed
Nov 22, 2023
sjinks
reviewed
Nov 22, 2023
sjinks
reviewed
Nov 22, 2023
sjinks
reviewed
Nov 22, 2023
rebeccahum
force-pushed
the
feature/devenv-purge-cmd
branch
3 times, most recently
from
November 22, 2023 21:57
f478b49
to
8d62e2b
Compare
sjinks
reviewed
Nov 22, 2023
sjinks
reviewed
Nov 22, 2023
sjinks
reviewed
Nov 22, 2023
rebeccahum
force-pushed
the
feature/devenv-purge-cmd
branch
from
November 22, 2023 22:09
9ee5a1c
to
ef8eb73
Compare
Co-authored-by: Volodymyr Kolesnykov <[email protected]>
rebeccahum
force-pushed
the
feature/devenv-purge-cmd
branch
from
November 22, 2023 22:17
2266e34
to
bc188bb
Compare
rebeccahum
force-pushed
the
feature/devenv-purge-cmd
branch
from
November 22, 2023 22:19
515b0be
to
0e8837a
Compare
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
sjinks
approved these changes
Nov 22, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Hello 👋🏼 here is an example of how we might add a
purge
command to VIP CLIdev-env
. It leveragesgetAllEnvironmentNames()
and loops through and awaitsdestroyEnvironment
on each name listed.Steps to Test
This will need to be plugged into typical testing workflows. I did
npm link
and alsonode --inspect
locally and it successfully destroyed all localdev-env
environments.