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.

Sign up for GitHub

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

Jump to bottom

Get-VagrantEnvironment should return the current path Vagrant environment #13

Closed
pauby opened this issue Mar 9, 2020 · 0 comments · Fixed by #17 · May be fixed by #16
Closed

Get-VagrantEnvironment should return the current path Vagrant environment #13

pauby opened this issue Mar 9, 2020 · 0 comments · Fixed by #17 · May be fixed by #16

Comments

@pauby
Copy link
Contributor

pauby commented Mar 9, 2020

I feel that Get-VagrantEnvironment should actually return the environment from the local path rather than the global environment. It just feel more PowerShelly and it's actually what I thought the function would do until I ran it.

Obviously this is a breaking change but as we are at a 0.1.9 build then I feel that change could be made.

To get a global environment I would propose we use a -Global or a -All switch or a Get-VagrantGlobalEnvironment function. My preference is -All.
corbob added a commit to corbob/Vagrantey that referenced this issue Nov 24, 2020
@corbob
(steviecoaster#13) Add All switch
6a0bd12 
all will do �agrant global-status while regular will now do �agrant status
corbob added a commit to corbob/Vagrantey that referenced this issue Nov 24, 2020
@corbob
(steviecoaster#13) Default to get local environment
eb5d78a 
Add a flag for All environments
This was referenced Nov 24, 2020
Open
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
1 participant
@pauby