secrets-provider-for-k8s
secrets-provider-for-k8s copied to clipboard
cyberark
Cyberark secrets provider for k8s
Because we are improving the batch retrieval experience we need to create a new release of the secrets provider DOD - [ ] Bump version from 1.1.0 -> 1.2.0 -...
We are adding new logs for the batch retrieval endpoint and therefore need TW review and approval DOD - [ ] TW and @InbalZilberman approval on logs
As part of the Batch Milestone, we need to create a new endpoint to efficiently handle batch secret requests This work can be split into 3: 1. Work in Conjur...
As part of the Batch Milestone, we need to create a new endpoint to efficiently handle batch secret requests This work can be split into 3: 1. Work in Conjur...
We need to run performance tests against the new Batch retrieval endpoint to update our performance SLA and give updated recommendations to how best to deploy Conjur with the Secrets...
Because we are adding a new Batch endpoint to our API we need to add integration test. In Conjur AND in Secrets Provider repos. DOD - [ ] Add integration...
Because we are adding a new Batch endpoint to our API we need to add integration test. In Conjur AND in Secrets Provider repos. DOD - [ ] Add integration...
As part of the Batch Milestone, we need to create a new endpoint to efficiently handle batch secret requests This work can be split into two: 1. Work in Conjur...
As part of our Secrets Provider release flow, our helm charts are packaged as part of our pipeline build and are saved to the artifacts tab in Jenkins. We then...
Currently, the release process requires manual update of the version in multiple locations. See [Update version](https://github.com/cyberark/secrets-provider-for-k8s/blob/master/CONTRIBUTING.md#update-the-version-changelog-and-notices) for more info. This is tedious and risky; version should be consistent and not...
