Partition Service Should Support Updating Existing Secrets in a Partition
Context & Scope
The Partition Service currently supports 3 API Operations.
- Create Partition (POST)
- Get Partition (GET)
- Delete Partition (DELETE)
Currently, the only way to add new secrets or update existing ones to the KV store for a partition is to delete it and recreate it. This leads to extra API calls and risks missing putting back some data that was not meant to be touched.
If this is implemented, KV stores will be simpler to update existing values on without having to delete existing data.
Partitions need to be updated with new secrets and edits to existing ones. In order to minimize the complexity of this operation for external callers, having a route to support this will simplify partition editing processes.
New API route in partition has to be supported/tested by all implementors of the service