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
Latest examples available on main don't work on the latest Ansible Galaxy release (0.3.3) #93
Comments
I think the issue is that you are using the configuration syntax that |
I seem to be seeing the same issue as reported here. |
Yeah, that seems to be issue. I've pulled the last commit and tested it and the config is generated as expected. |
Indeed, seems that pulling the latest from makes it work. Will this fix make it to the ansible-galaxy repository? |
It will make it to ansible-galaxy when I'll leave this issue open until |
@alessfg I just burned a couple of hours chasing down why my seemingly valid sytax wasn't working with |
Sadly, no. Other higher priority tasks have kept me from dedicating as much time as I'd like to the Ansible roles. That being said, what I can do is add a disclaimer to the README for the time being pointing people to the |
Aaand done 030e282 -- I'm also going to change this issue's title and pin it to try to avoid people loosing unnecessary time figuring out why the latest examples are not working. |
…n branch of nginx_config. Followed up on nginxinc/ansible-role-nginx-config#93 to see when 0.4.0 will be available.
Hey @alessfg, Is there a ticket somewhere with what has been completed and needs to be done for the 0.4.0 release? I would like to make some simple examples/docs, just not sure what state everything is in. |
If everything goes according to plan, I originally planned to release it about a month ago once I finished my refactoring efforts, but as is tradition, there were some last minute developments regarding upcoming NGINX releases that delayed the release. |
I am happy to report that Closing this for the time being since the original issue posted here should hopefully no longer be an issue. |
posting my ansibleplaybook example for basic setup with 0.4.0. @rolandjitsu |
Has the config spec changed? Because I've tried updating to 0.4.0 yesterday and the generated output wasn't similar to what it was when using fa49aa0. |
Yep, it has. Long story short I've been slowly refactoring the whole config spec over the last year to make it more sustainable long term. I've tried my best to go in depth over the changes on the CHANGELOG but to be completely honest given that everything has changed in some shape or another it might be easier to recreate the config altogether instead of trying to port it. Not the best scenario I know, but on better news I do not expect the config spec to undergo any further drastic changes down the line. |
Ok, I understand. I guess I'll just have to spend a bit of time updating to the new spec. |
For sure. Feel free to open a new issue if you have any questions! |
Unpinning this issue as with the latest release the latest examples on main do work with the latest Ansible Galaxy release (0.4.2). |
Describe the bug
I'm trying to setup a simple HTTP server on a Debian machine with the following config:
But it seems like the config file on the remote host is always empty or contains just the comment:
To reproduce
Steps to reproduce the behavior:
/etc/nginx/conf.d/default.conf
contentsExpected behavior
I'd expect the config file on the remote host to be generated with the config I've setup.
Your environment:
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: