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

Move base package list to group_vars #5

Closed
inghamn opened this issue Jan 31, 2018 · 3 comments
Closed

Move base package list to group_vars #5

inghamn opened this issue Jan 31, 2018 · 3 comments

Comments

@inghamn
Copy link
Member

inghamn commented Jan 31, 2018

We want to allow for hosts to customize the base package list. The packages should not be hard coded in the role. For instance, we now have a line for VM-tools; however, we use this on physical machines as well.

We should be able to customize the base packages.

@charlesbrandt
Copy link

Are you referring to the group_vars associated with the role or with the inventory?

I would prefer to put only those items that are not universal in the group_vars. Moving everything to group_vars makes the playbooks harder to read and less useful for others who may not have access to our inventory.

@inghamn
Copy link
Member Author

inghamn commented Apr 16, 2018

With the standardization of CKAN uploading, we want to make sure CURL is available on any machines that will be uplolading to CKAN. We probably don't want CURL on all linux machines, so it might make sense to put it's declaration in group_vars.

@inghamn
Copy link
Member Author

inghamn commented Apr 16, 2018

We'll need to remove the custom config files for nano, vim, and tmux. I expect users will set up their own user-specific config files when they first log into the systems.

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

No branches or pull requests

2 participants