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

Switch to using nginx puppet resources to manage the stackstorm nginx config #311

Merged
merged 5 commits into from
Aug 17, 2020

Conversation

nmaludy
Copy link
Member

@nmaludy nmaludy commented Aug 13, 2020

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.

@nmaludy nmaludy self-assigned this Aug 13, 2020
Copy link
Member

@arm4b arm4b left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

But I generally dislike the Puppet granular approach trying to manage every single field. If upstream st2 nginx config is changed, - things will need a dedicated sync-up every time.

This is good as far someone manages it. So thanks for that work @nmaludy!

@arm4b
Copy link
Member

arm4b commented Aug 17, 2020

This PR also reminds me we'll need a follow-up on StackStorm/community#44

@nmaludy nmaludy merged commit 70d49d3 into master Aug 17, 2020
@nmaludy nmaludy deleted the feature/nginx-config branch August 17, 2020 20:20
bishopbm1 pushed a commit to EncoreTechnologies/puppet-st2 that referenced this pull request May 20, 2022
Switch to using nginx puppet resources to manage the stackstorm nginx config
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Use nginx server and config resources instead of copying the default file
2 participants