-
Notifications
You must be signed in to change notification settings - Fork 9
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
Partial playbook execution not working: dhcp #57
Comments
it may also help to use a block for the last set of tasks: clean, copy, upload, reload.... all should be processed always when the config has changed, etc. |
Hello @rvalle I'll have a look at the fetch issue and be back soon ... The block hint has to be considered in #12 |
I see @zerwes in your setup you do an tagged import role, while in the vanilla role it is an include_tasks. Perhaps they behave differently. I think they have to be applied always instead of fetch. Yes, finer grain handlers would be a great tool too. I think these features will make a difference during configuration work on the firewalls, making it more agile. |
well, by enforcing the tag inheritance for the |
#58 works for me ... |
thanks!!! |
I am attempting to use tags to update my router partially.
the actual use case I am using is update only dhcp entries.
For some reason fetch is not working, although I can see that there is an always tag. I works only if I explicitly include the "fetch" tag. I am not sure what the reason is, but it could be that the always applies only to the include-tasks, and the tasks inside are all "fetch" only.
Then there is the application and reload, I think they also need the always tag. when: config.changed will not be processed unless the task is selected by tags first, I think.
Partial execution would be a nice to have feature as configuration of the router keeps growing. would provide more agility while building the router configuration.
The text was updated successfully, but these errors were encountered: