You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: the Backstage installation in my organisation uses an older Backstage version, so plugins are loaded in code, not the new config-based plugin loader.
👍 Expected behavior
The 'Add permission policies' section should let me add permissions to my policy from the enabled plugins (e.g. catalog.read, catalog.create).
👎 Actual Behavior with Screenshots
The 'plugins' dropdown is sometimes empty, so I cannot add any permissions. (See screenshot.)
👟 Reproduction steps
Create a Backstage app with the RBAC plugin in use.
Enable some of your other plugins (which declare permissions) for permissions checking in the RBAC plugin configuration (i.e. in the awaitPermissionRbac callback, shown above)
Plugin Name
rbac
📜 Description
When I try to create a new RBAC role in the 'Create Role' screen (when running locally that's at http://localhost:3000/rbac/role/new),
And I use the Plugin dropdown in the 'Add permission policies' section,
Then the dropdown list is sometimes empty. (There are no plugins to choose from.)
This happens even though I have enabled some plugins (in particular
catalog
) for the permissions system in my app'sindex.ts
:Note: the Backstage installation in my organisation uses an older Backstage version, so plugins are loaded in code, not the new config-based plugin loader.
👍 Expected behavior
The 'Add permission policies' section should let me add permissions to my policy from the enabled plugins (e.g.
catalog.read
,catalog.create
).👎 Actual Behavior with Screenshots
The 'plugins' dropdown is sometimes empty, so I cannot add any permissions. (See screenshot.)
👟 Reproduction steps
awaitPermissionRbac
callback, shown above)📃 Provide the context for the Bug.
I am trying to create an RBAC role with the Backstage community RBAC plugin.
👀 Have you spent some time to check if this bug has been raised before?
🏢 Have you read the Code of Conduct?
Are you willing to submit PR?
None
The text was updated successfully, but these errors were encountered: