Vagrant Environment Operations: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 1: Line 1:
=External=
=External=
=Internal=
=Internal=
* [[Vagrant_Concepts#Environment_Operations|Vagrant Concepts - Environment]]
* [[Vagrant_Concepts#Environment_Operations|Vagrant Concepts]]
* [[Vagrant Operations#Environment Operations|Vagrant Operations]]
* [[Vagrant Operations#Environment Operations|Vagrant Operations]]



Revision as of 19:58, 17 November 2019

External

Internal

Operations

init

https://www.vagrantup.com/docs/cli/init.html
vagrant init

global-status

https://www.vagrantup.com/docs/cli/global-status.html
vagrant global-status

This command tells the state of all active Vagrant environments for the currently logged in user:

id       name         provider state   directory
------------------------------------------------------------------------
1a4c3f3  blue         aws      running /Users/ovidiufeodorov/tmp/blue
266ef17  red          aws      running /Users/ovidiufeodorov/tmp/red

The command does not actively verify the state of machines, it is instead based on a cache, so you may see stale results.

To refresh the cache:

vagrant global-status --prune