Switch to using nginx puppet resources to manage the stackstorm nginx config #311
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.
Closes #262
This changes the way Puppet manages the StackStorm nginx config from basically just copying the file shipped with the RPM/DEB packages, over to Puppe native nginx resources.
The end result her is that the management of the nginx config is not idempotent (it was not before). It also allows us to do things like tweak the SSL settings (protocols, ciphers, etc) used by nginx to create a security hardened setup.