-
Notifications
You must be signed in to change notification settings - Fork 24k
constructed inventory, allow adding variables directly, including ansible_group_priority #81603
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
base: devel
Are you sure you want to change the base?
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
I'm waiting on this to get merged and released to enable the inventory setup that I've architected. Anything I can do to get this pushed through? |
Time, which I don't have much of. I'm fine if you want to take over this PR and complete it, it at least needs tests. The other thing i was mulling over is making priority templatable or not and injecting |
I took a stab at fixing an error I ran into, and adding tests. I have the changes here in a fork that I made: 0a6fa06 I'm not sure what the workflow would be to get this into the PR. I guess I could open a PR against the branch in your repo, which when merged would reflect in this PR? IDK, I just don't wanna mess anything up workflow-wise for you. I mean, I haven't ever even contributed code to Ansible before, so I don't know what a typical workflow looks like, much less whatever's going on here. Re: the templating of the priority variable: I don't think that would address either mine or the original issue, since we were both utilizing it to set a static priority number. Adding that wouldn't solve any issue that's currently been brought up. I'm definitely lost at what you mean by "injecting Thanks for all the work that you do, and I hope that whatever I can do on this can save you some time and effort. |
as for workflow, you can add a 'suggested commit' to this PR itself the templating/keyed_group_name was so you could do the following:
assuming |
I wasn't able to find suggested commits on this PR, so I opened bcoca#13 with my changes. If that's not going to work, hopefully we can figure something else out. |
Hello, Really helpfull thanks by advance |
bf56e53
to
9fc0eba
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a couple typos, otherwise LGTM
* Fix setting group priority and add tests Add all the tests to ensure the overrides for priority work as advertised, and fix the set_priority function so that it operates on a group rather than on a string in `__init__.py` * Implement ansible_keyed_group_name Add more comments Add example Change where we're setting the group_priority to allow it to be templated with all available variables and `ansible_keyed_group_name` * Reverse precedence of combining variables * Move group priority to after the `add_host` call in case the group does not exist yet
Co-authored-by: Matt Davis <6775756+nitzmahone@users.noreply.github.com>
Co-authored-by: Matt Davis <6775756+nitzmahone@users.noreply.github.com>
Co-authored-by: Matt Davis <6775756+nitzmahone@users.noreply.github.com>
…oup_str_default_value_with_priority.yml Co-authored-by: Matt Davis <6775756+nitzmahone@users.noreply.github.com>
The test
|
implementing #76788
ISSUE TYPE