-
-
Notifications
You must be signed in to change notification settings - Fork 875
Unable to set auth_basic for "alias" location type #600
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
Comments
@jmswick are you setting the value YAML treats several values as boolean, so when you set |
Yes, I am setting it in heira and I tried quoting it in several different ways, which eliminated the error, but I still didn't get a "auth_basic off" in the nginx config on the system. (I should have stated that from the beginning too.) If I have time today I'll try to recreate this in a vagrant test VM so that I can provide the config. One change is that we are using eyaml so that we can encrypt specific yaml entries, so that could be enough of a difference. Our vagrant test setup doesn't use eyaml so that should help to narrow it down. |
Can you post your manifest for the location resource?
|
Hi,
It generated this /etc/nginx/sites-enabled/testapp.conf file:
|
Right now I've updated the issue title to better reflect this problem. |
Thank you. I hadn't dug that far into the module to see that case. |
Thank you. I do get the expected nginx config now and a basic test works as a proof of concept. |
I've been working on an nginx host that has a default auth_basic for the vhost. However, I am needing to add a single location with auth_basic off so that it can have a health check for a load balancer infront of it.
However, when setting auth_basic to 'off' I get the following error due to puppet treating 'off' as 'false':
Due to this check in location.pp:
The text was updated successfully, but these errors were encountered: