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

Need a --force flag #46

Closed
treed593 opened this issue Mar 9, 2017 · 3 comments
Closed

Need a --force flag #46

treed593 opened this issue Mar 9, 2017 · 3 comments

Comments

@treed593
Copy link

treed593 commented Mar 9, 2017

What is the best way to destroy a box and recreate it with updated config/scripts?

@obilodeau
Copy link
Member

vagrant box list will list the boxes and vagrant box remove <boxname> to remove

Do you think we should have an overwrite option?

malboxes build --overwrite <profile>

The reason I didn't do it initially is because box management is more vagrant's job but it's true that we doing some box management. Or, we could document the common vagrant commands to learn.

@treed593
Copy link
Author

treed593 commented Mar 9, 2017

I think either would work, but the --overwrite may be a good addition, especially for those not familiar with Vagrant.

@treed593
Copy link
Author

treed593 commented Mar 9, 2017

It may even be an okay idea to use the --force flag when importing the box to Vagrant. I am testing a couple configuration changes and am rebuilding the box a lot, so this is something I am running into.

@obilodeau obilodeau changed the title Destroy and Rebuild Box Need a --force flag Jul 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants