-
Notifications
You must be signed in to change notification settings - Fork 0
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
add flavor to project mapping #52
base: main
Are you sure you want to change the base?
Conversation
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.
Please, could you expand README for the role with the additional functionality?
I have added some info to readme. Let me know if this is enough. |
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.
@cityofships Done
interface: "{{ os_flavors_interface | default(omit, true) }}" | ||
name: "{{ item.0.name }}" | ||
state: "{{ item.0.state | default('present') }}" | ||
project: "{{ item.1 | default(omit) }}" |
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.
It does look like it is still possible to have is_public: True
and a list of projects for flavor access. Perhaps you should add a predicate based on item.0.is_public
here to make sure we only process flavors that are marked as private.
This will add ability to map flavours to projects in Openstack.
It uses capabilities provided by module: https://github.com/openstack/ansible-collections-openstack/blob/master/plugins/modules/compute_flavor_access.py