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

[WIP] Allow more specific restriction types for roles #22650

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

jaywcarman
Copy link
Member

@jaywcarman jaywcarman commented Aug 10, 2023

Follow up to #22573, which introduced separate restrictions for Catalog Items.

This changes further splits the role restriction settings to include the following types:

  • Catalog Items
  • Key Pairs
  • Orchestration Stacks
  • Services
  • VMs and Templates

Depends on:

Follow 6072d2c in allowing more specific restriction types. Default
values of ':user' following the original global default value.
@jaywcarman jaywcarman force-pushed the allow_more_specific_restriction_types_for_roles branch from 73c6034 to 53b9aad Compare August 10, 2023 19:28
@miq-bot
Copy link
Member

miq-bot commented Aug 10, 2023

Checked commit jaywcarman@53b9aad with ruby 2.6.10, rubocop 1.28.2, haml-lint 0.35.0, and yamllint
1 file checked, 0 offenses detected
Everything looks fine. 🏆

@miq-bot miq-bot added the stale label Nov 13, 2023
@miq-bot
Copy link
Member

miq-bot commented Nov 13, 2023

This pull request has been automatically marked as stale because it has not been updated for at least 3 months.

If these changes are still valid, please remove the stale label, make any changes requested by reviewers (if any), and ensure that this issue is being looked at by the assigned/reviewer(s)

Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation.

@miq-bot
Copy link
Member

miq-bot commented Feb 19, 2024

This pull request has been automatically marked as stale because it has not been updated for at least 3 months.

If these changes are still valid, please remove the stale label, make any changes requested by reviewers (if any), and ensure that this issue is being looked at by the assigned/reviewer(s).

2 similar comments
@miq-bot
Copy link
Member

miq-bot commented May 20, 2024

This pull request has been automatically marked as stale because it has not been updated for at least 3 months.

If these changes are still valid, please remove the stale label, make any changes requested by reviewers (if any), and ensure that this issue is being looked at by the assigned/reviewer(s).

@miq-bot
Copy link
Member

miq-bot commented Aug 26, 2024

This pull request has been automatically marked as stale because it has not been updated for at least 3 months.

If these changes are still valid, please remove the stale label, make any changes requested by reviewers (if any), and ensure that this issue is being looked at by the assigned/reviewer(s).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants