diff --git a/.gitignore b/.gitignore index 3068954f..ec041a7c 100644 --- a/.gitignore +++ b/.gitignore @@ -15,5 +15,3 @@ predicate.json _bin .envrc - -examples/encrypted-secrets/output.json diff --git a/README.md b/README.md index 6a433fad..94d3ed0c 100644 --- a/README.md +++ b/README.md @@ -34,7 +34,6 @@ go run . agent \ > - [./agent.yaml](./agent.yaml). > - [./examples/one-shot-secret.yaml](./examples/one-shot-secret.yaml). > - [./examples/cert-manager-agent.yaml](./examples/cert-manager-agent.yaml). -> - [./examples/encrypted-secrets](./examples/encrypted-secrets) - Send encrypted Kubernetes secrets to CyberArk. You might also want to run a local echo server to monitor requests sent by the agent: diff --git a/RELEASE.md b/RELEASE.md index d386a0a7..78519b6c 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -1,7 +1,8 @@ # Release Process > [!NOTE] -> Before starting, let Michael McLoughlin know that a release is about to be created so that documentation can be prepared in advance. +> Before starting a release let the docs team know that a release is about to be created so that documentation can be prepared in advance. +> This is not necessary for pre-releases. The release process is semi-automated. @@ -63,11 +64,11 @@ The release process is semi-automated. 7. Publish the release. -8. Inform the `#venctl` channel that a new version of Discovery Agent has been - released. Make sure to share any breaking change that may affect `venctl connect` - or `venctl generate`. +8. Inform the `#venafi-kubernetes-agent` channel on Slack that a new version of the Venafi Discovery Agent has been + released (and that a new version of the disco-agent has been released!)a + TODO: Who should be notified on the disco side? -9. Inform Michael McLoughlin of the new release so he can update the +9. Inform the docs team of the new release so they can update the documentation at . [tests-workflow]: https://github.com/jetstack/jetstack-secure/actions/workflows/tests.yaml?query=branch%3Amaster