Skip to content
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

Allow specifying the organization in content roles #1653

Open
smeeus opened this issue Jul 30, 2023 · 2 comments · May be fixed by #1815
Open

Allow specifying the organization in content roles #1653

smeeus opened this issue Jul 30, 2023 · 2 comments · May be fixed by #1815

Comments

@smeeus
Copy link
Contributor

smeeus commented Jul 30, 2023

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
@smeeus
Copy link
Contributor Author

smeeus commented Jul 30, 2023

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?

@JaketheZ
Copy link

JaketheZ commented Jan 17, 2025

I found that the same applies also for content_credentials and manifest

@JaketheZ JaketheZ linked a pull request Jan 17, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants