puppet-nginx refactor to class/arguments #25
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These commits (hopefully) will add the first arguments to puppet-nginx and hopefully will set the basic idea for anyone to help refactor puppet-nginx make sure of not breaking current users of puppet-nginx.
The idea is that nothing should be trusted and everything must have a sane default value, arguments MUST have defaults from params.pp set on main class as well as for any subclass that needs it, so no matter no one should be calling subclasses (eg nginx::config) by themselves, we should set a default for it too, as someone may be calling it and not setting a default in the subclass call will break his configuration.