Skip to content
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

Adding vm:nuke command. #1069

Merged
merged 3 commits into from
Feb 9, 2017
Merged

Adding vm:nuke command. #1069

merged 3 commits into from
Feb 9, 2017

Conversation

grasmash
Copy link
Contributor

@grasmash grasmash commented Feb 9, 2017

No description provided.

@grasmash grasmash added in progress Enhancement A feature or feature request labels Feb 9, 2017
<equals arg1="${vm.nuke}" arg2="y" casesensitive="false"/>
<then>
<exec dir="${repo.root}" command="vagrant destroy" logoutput="true" checkreturn="true" level="${blt.exec_level}" passthru="true"/>
<exec dir="${repo.root}" command="rm -rf Vagrantfile box blt/project.local.yml drush/site-aliases/aliases.drushrc.php" logoutput="true" checkreturn="true" level="${blt.exec_level}" passthru="true"/>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@grasmash - This is slightly more dangerous than I think it need be...

  • The user could have other customizations in the box dir that are useful to preserve (e.g. scripts, local.config.yml, etc.).
  • The blt/project.local.yml can also have helpful additions for that particular user too, which would need to be recreated.

I don't know if there's a better way to guarantee that a new blt vm works correctly though :/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement A feature or feature request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants