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

archive install check if user and/or service was already defined #37

Closed
hurrycaine opened this issue Jul 24, 2015 · 0 comments
Closed

Comments

@hurrycaine
Copy link
Contributor

At my work we are very specific with how we create our users and groups (uid, home dir etc...).
I also did not like the service that is default with archive install. Chances are someone would create a start up script or something here.

At first I was going to add a manage user/service parameter but since this supports many different types of install methods I thought this would get confusing. Also, I am sensitive to parameter growth.

I have test and have a pull request with a solution. No impact by default. The user and the service under archive only... check to see if they are defined first. This allows someone to create the user prior to call grafana class. The service is a bit tricker as you want it after the install/config but before the grafana::service.
This does not cover the scenario of wanting to create a different user then grafana but I feel this would be pretty fringe.

I have included an advance usage in readme to go over this scenario with examples.

Please let me know if you have any questions

@bfraser bfraser closed this as completed in 98699ee Aug 4, 2015
bfraser added a commit that referenced this issue Aug 4, 2015
fixes #37 : archive install now checks if user/service are defined be…
cegeka-jenkins pushed a commit to cegeka/puppet-grafana that referenced this issue Oct 23, 2017
cegeka-jenkins pushed a commit to cegeka/puppet-grafana that referenced this issue Oct 23, 2017
fixes bfraser#37 : archive install now checks if user/service are defined be…
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

1 participant