foreman-ansible-modules
foreman-ansible-modules copied to clipboard
Allow specifying the organization in content roles
SUMMARY
The content roles activation_keys
, content_views
, content_view_publish
, lifecycle_environments
, repositories
and sync_plans
have the organization
parameter set to the variable foreman_organization
.
When working with multiple organizations, it would be helpful if an organization can be specified in the respective role variable arrays.
To keep the roles backward compatible, the foreman_organization
can still be specified as default value when the organization is not specified.
ISSUE TYPE
- Feature Idea
Question: Should content roles be allowed to add products and repositories to multiple organizations?
If yes: should the modules be updated to allow this by having an organizations
parameter, or should the roles handle this for the modules?