Skip to content
This repository has been archived by the owner on Oct 5, 2021. It is now read-only.

updating one of the sites data_bags #79

Open
retrodans opened this issue Feb 1, 2014 · 3 comments
Open

updating one of the sites data_bags #79

retrodans opened this issue Feb 1, 2014 · 3 comments

Comments

@retrodans
Copy link

Sorry if this is a bit of a beginner question, but I have got vagrant working as I expect it to, with a few of my own .json files in the data_bags/sites folder. One issue I have come across it that when I come to modify these files, I cannot get it to honor these changes in the box if it has already been build. I have tried both vagrant provision and vagrant reload --provision with no luck.

The only thing that has worked is vagrant destroy followed by a vagrant up (or just ssh'ing into the box, and manually making the changes). Have I missed something, as believed that a provision would rerun the chef scripts and update the paths accordingly. Some example changes are:

  • adding/removing sites files
  • altering the docroot path

Thanks for any help you can give on this, as not sure if this is my understanding of vagrant, or an issue with the setup.

@vegon
Copy link

vegon commented Feb 18, 2014

I have the same issue.

@Vhornets
Copy link

Same issue

@eelkeblok
Copy link
Contributor

Adding a data_bag should work fine, as long as you let the box provision again (e.g. reload --provision). Updating might well be an issue, I know indeed from personal experience that vhost configurations are not removed when data_bags are no longer present. This is probably something in the recipe that handles the databags, maybe it should just empty and rebuild the sites-available and sites-enabled directories. Personally, it doesn't bother me much, I rarely need to remove or update a databag. If you do need to make changes often, I wonder what the use case is.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants