Remove the tenant-secret association table
Currently all secrets are indirectly associated with tenants via a tenant-secret association table. This association was configured early in the project lifecycle, when it seemed that such an association would aid in retrieving different components of a grouped secret with different RBAC behaviors. However, recent cross-project discussion have indicated that this feature would be better implemented in a different way. Hence this association is adding an additional join on selects with no benefit, and therefore should be removed.
Blueprint information
- Status:
- Complete
- Approver:
- Douglas Mendizábal
- Priority:
- High
- Drafter:
- John Wood
- Direction:
- Approved
- Assignee:
- Juan Antonio Osorio Robles
- Definition:
- Approved
- Series goal:
- Accepted for liberty
- Implementation:
- Implemented
- Milestone target:
- 1.0.0
- Started by
- Douglas Mendizábal
- Completed by
- Douglas Mendizábal
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Add project_id to Secret model
Addressed by: https:/
Fill project_id in secrets where needed
Addressed by: https:/
Remove ProjectSecret table-related code