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

add create_resources and rename environment parameter #1

Closed
wants to merge 8 commits into from

Conversation

jnoss
Copy link

@jnoss jnoss commented May 15, 2017

This pulls in upstream PR voxpupuli#64 and voxpupuli#77 (with minor modifications after pulling in voxpupuli#77)

lvicainne and others added 8 commits January 2, 2017 12:24
…e create_resource to instanciate some certonly ressource
…e create_resource to instanciate some certonly ressource
This is a fix for voxpupuli#63.
We rename the `environment` to `venv_vars` in order to ensure that hiera
calls do *not* break, as soon as a puppet execution flow enters our
module. For consistency's sake, we change `environment` not only in the
main class (where it's definitely needed:
rodjek/puppet-lint#574), but also in the
`certonly` define.
…urces

 Conflicts:
	manifests/certonly.pp
	spec/classes/letsencrypt_spec.rb
	spec/defines/letsencrypt_certonly_spec.rb
This changes the name to avoid potential confusion with the
letsencrypt::certonly defined type; now the certs to be created via this
create_resources are specified via the hiera or class param
letsencrypt::certs.
This updates what the certonly type requires - to be used via the
create_resources in init, can't depend on the whole class. For now just
depend on the exec.
@jnoss
Copy link
Author

jnoss commented May 16, 2017

Closing this, going to keep our master branch tracking upstream.

@jnoss jnoss closed this May 16, 2017
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

Successfully merging this pull request may close these issues.

3 participants