You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We would like to have a tar of the relevant docker image in the github release page. We have it for this release. In this case, we did it manually by running locally:
docker pull cyberark/conjur-authn-k8s-client:0.18.1
docker save -o conjur-authn-k8s-client-0.18.1.tar cyberark/conjur-authn-k8s-client:0.18.1
and manually uploading the tar to the release page.
We would like this to happen automatically once we push a new tag and release it. This can be done by running the steps above in the Jenkins pipeline and archiving the artifact. We can also look into this github action to perform this.
DoD:
image tar is automatically uploaded to release pages
Process is documented (if needed)
A list of projects that can do the same process is created
PRs are created for those projects to perform the same action
The text was updated successfully, but these errors were encountered:
@orenbm why was a tar of the client uploaded to the release of the SP? is that a requirement? Shouldnt the tar be of the Secrets Provider no the client?
We would like to have a tar of the relevant docker image in the github release page. We have it for this release. In this case, we did it manually by running locally:
and manually uploading the tar to the release page.
We would like this to happen automatically once we push a new tag and release it. This can be done by running the steps above in the Jenkins pipeline and archiving the artifact. We can also look into this github action to perform this.
DoD:
The text was updated successfully, but these errors were encountered: