[Vagrant] debops not installed if /vagrant is not mounted
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 1.4k
- Forks
- 379
- Avg merge
- 4d 18h
- Merged PRs (30d)
- 8
Description
If you want to use DebOps Vagrantfile on a host system like Windows where /vagrant is not mounted, vagrant will fail and debops will not be install.
Steps to reproduce
- Disable mount of
/vagrant - Run
vagrant up
Actual results
vagrant fail
Expected results
vagrant should not fail and debops should be install.
Proposal
/vagrant is only necessary if you want to build debops from sources.
When /vagrant is not mounted, we could install debops from PyPI and use code already present to install master branch using debops-update.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Vagrantfile sections linked in the issue, especially the logic around lines 587-593 and 816-819. Reproduce the failure with the /vagrant mount disabled and inspect how debops-update is used. Done means vagrant up succeeds without /vagrant and debops is installed from PyPI or the master branch.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100