-
Spike
-
Resolution: Unresolved
-
Normal
-
Global Hub 1.3.0
Value Statement
In ACM-12500 we investigated how to work with SpiceDB APIs as is. The Authz team is working on https://github.com/project-kessel/
We need to understand the impact of the changes and what it means. And modify the findings of ACM-12500
Definition of Done for Engineering Story Owner (Checklist)
- ...
Development Complete
- The code is complete.
- Functionality is working.
- Any required downstream Docker file changes are made.
Tests Automated
- [ ] Unit/function tests have been automated and incorporated into the
build. - [ ] 100% automated unit/function test coverage for new or changed APIs.
Secure Design
- [ ] Security has been assessed and incorporated into your threat model.
Multidisciplinary Teams Readiness
- [ ] Create an informative documentation issue using the Customer
Portal Doc template that you can access from [The Playbook](
and ensure doc acceptance criteria is met.
- Call out this sentence as it's own action:
- [ ] Link the development issue to the doc issue.
Support Readiness
- [ ] The must-gather script has been updated.
- is related to
-
ACM-12504 Investigate if SpiceDB can serve as highly scalable Graph DB layer
- To Do