| openstackgerrit | Tosin Farai proposed openstack/ansible-collections-openstack master: Add support for new features https://review.opendev.org/c/openstack/ansible-collections-openstack/+/766776 | 00:01 |
|---|---|---|
| openstackgerrit | Shnaidman Sagi proposed openstack/ansible-collections-openstack master: Add modules for roles information https://review.opendev.org/c/openstack/ansible-collections-openstack/+/769202 | 00:20 |
| openstackgerrit | Shnaidman Sagi proposed openstack/ansible-collections-openstack master: Add modules for roles information https://review.opendev.org/c/openstack/ansible-collections-openstack/+/769202 | 01:25 |
| openstackgerrit | Shnaidman Sagi proposed openstack/ansible-collections-openstack master: Add modules for roles information https://review.opendev.org/c/openstack/ansible-collections-openstack/+/769202 | 02:30 |
| *** spatel has joined #openstack-ansible-sig | 02:44 | |
| *** evrardjp has quit IRC | 05:33 | |
| *** evrardjp has joined #openstack-ansible-sig | 05:33 | |
| *** spatel has quit IRC | 06:17 | |
| *** tosin has joined #openstack-ansible-sig | 07:14 | |
| *** tremble has quit IRC | 07:41 | |
| *** gtema has joined #openstack-ansible-sig | 08:17 | |
| *** tremble has joined #openstack-ansible-sig | 08:29 | |
| sshnaidm | gtema, replied ^ | 10:09 |
| gtema | ok, will have a look after the call | 10:18 |
| gtema | and if we have "name" - we can use get_role - I guess we do it like that sometimes: list or get | 10:19 |
| *** tosin has quit IRC | 10:22 | |
| *** tosin has joined #openstack-ansible-sig | 12:28 | |
| sshnaidm | gtema, if data is same it doesn't make sense to use a different call | 13:33 |
| sshnaidm | probably I can just filter the output and return role with "name" | 13:34 |
| gtema | idea is to be able to get ID by name and verify existence | 13:34 |
| gtema | or name by ID | 13:35 |
| sshnaidm | gtema, the return data prints both name and ID | 13:37 |
| gtema | I know. I am using often _info really to only verify presence of concrete entry | 13:38 |
| gtema | something like image | 13:38 |
| gtema | or after deleting resource verify it is really gone | 13:38 |
| sshnaidm | gtema, for that purpose it's better to use not-info module, like identity_role module | 13:40 |
| *** gtema has quit IRC | 13:40 | |
| sshnaidm | for ensuring the role exists/doesn't exist | 13:40 |
| *** gtema has joined #openstack-ansible-sig | 13:41 | |
| sshnaidm | gtema, in bottom line I think I can add filter by ID/name if specified | 13:46 |
| gtema | there is no need to fetch all roles in this case. But we can add it in SDK, since API supports this | 13:47 |
| gtema | you can also invoke "search_roles" | 13:48 |
| sshnaidm | gtema, I'd leave same call for simplicity, when sdk supports it we'll need just to add 'name' for kwargs | 13:48 |
| gtema | and actually list_roles should support passing "name" under kwargs | 13:49 |
| sshnaidm | yeah, I see list_users supports it | 13:50 |
| sshnaidm | I'll try to add it in SDK | 13:50 |
| gtema | SDK should support it as well out-of-box | 13:50 |
| gtema | it's just not properly documented | 13:50 |
| sshnaidm | it's not in valid_kwargs, trying to add it there | 13:57 |
| gtema | oh, right | 14:01 |
| sshnaidm | gtema, yeah, seems working, preparing a patch.. | 14:04 |
| gtema | cool | 14:05 |
| sshnaidm | gtema, till which branch we can backport it? | 14:06 |
| gtema | hmm | 14:06 |
| gtema | actually pretty far, as long as policies allow. But I would go till train, since we had a restructure | 14:07 |
| *** tremble has quit IRC | 16:16 | |
| *** gtema has quit IRC | 17:28 | |
| *** tremble has joined #openstack-ansible-sig | 18:24 | |
| *** tosin has quit IRC | 22:07 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!