backstage-goalie[bot]
commented
1 month ago Changed Packages
| Package Name | Package Path | Changeset Bump | Current Version |
|---|---|---|---|
| @backstage/backend-app-api | packages/backend-app-api | patch | v0.7.6-next.0 |
| @backstage/backend-plugin-api | packages/backend-plugin-api | patch | v0.6.19-next.0 |
| @backstage/backend-test-utils | packages/backend-test-utils | patch | v0.3.9-next.0 |
| @backstage/plugin-permission-node | plugins/permission-node | patch | v0.7.30-next.0 |
github-actions[bot]
As part of BEP-0007.
The config format is a little different from the internal names of things, for convenience. Open to suggestions here.
I put it as a visible type on the service principal, even though I really originally intended for it to be hidden on the internal credential type instead. This would let us iterate more easily on it in secrecy. But reaching that field becomes cumbersome since the types involved are only in backend-app-api, but need to be consumed from plugin-permission-node. In the end, I decided to hope that these interfaces are stable enough, that there isn't significant risk in setting this in stone in backend-plugin-api. Again, feedback is welcome.
Another potential middle ground could be to make the scope type something semi opaque like
Record<string, string[]>and have different subsystems use keys in that as they see fit.Regard this as being up for early review, as I'm away for a little bit now.