StackStorm / StackStorm/st2-rbac-backend

Execute permission to all packs and actions

Open
#77 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
5
Forks
13
PR merge metrics
No merged PRs in 30d

Description

Hi,

I'm trying to create a role which will have execute permission for all packs all actions.
Is there a way to assign "action_execute" permission only to all packs /all actions in an easy way, either using regular expression or array list?
Below is how i am trying to configure this. If this is possible, what might i be doing wrong?

        resource_uid: "pack:*"
        permission_types:
            - "action_view"
            - "action_execute"

OR

        resource_uid: "action:*"
        permission_types:
            - "action_view"
            - "action_execute"

Other global permission granted to the role -
permission_grants:
-
permission_types:
- "pack_list"
- "action_list"
- "rule_list"
- "execution_views_filters_list"
- "execution_list"

THanks!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or implementation entry points are named in the issue. Start by locating the RBAC handling for resource_uid and permission_types, then determine whether wildcard grants for all packs or actions are supported; done means the requested role configuration works or the supported limitation is documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
authorization, backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.