-
Feature
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
False
-
-
False
Feature Overview (aka. Goal Summary)
We have old feature request from community https://github.com/backstage/community-plugins/issues/5358 and pull requests with implementation proposals:
https://github.com/backstage/community-plugins/pull/4350
https://github.com/backstage/community-plugins/pull/3521
https://github.com/backstage/community-plugins/pull/3908
It would be nice to finally help community to archive desired feature. Also this feature can be used to enable rbac plugin by default in the RHDH.
Goals (aka. expected user outcomes)
Provide rbac role with default permissions for all users and groups.
Requirements (aka. Acceptance Criteria):
A list of specific needs or objectives that a feature must deliver in order
to be considered complete. If the feature spans across releases then good
to have scope for each release with acceptance criteria. Be sure to
include nonfunctional requirements such as security, reliability,
performance, maintainability, scalability, usability, etc.
<enter general Feature acceptance here>
Out of Scope (Optional)
High-level list of items that are out of scope.
<your text here>
Customer Considerations (Optional)
Provide any additional customer-specific considerations that must be made
when designing and delivering the Feature. Initial completion during
Refinement status.
<your text here>
Documentation Considerations
Provide information that needs to be considered and planned so that
documentation will meet customer needs. If the feature extends existing
functionality, provide a link to its current documentation.
<your text here>