-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Push git tags back upstream on deploy / promote #39
Comments
@orta mentioned https://aws.amazon.com/secrets-manager/ and i was wondering one approach could be have hokusai setup with different secret managers, maybe at first we can offer:
type of thing, where |
@ashkan18 not sure how this relates to this issue which I opened to consider syncing git tags with ECR tags |
@ashkan18 regarding supporting aws secrets manager, I think that's a bit out of scope for Hokusai as an external (to k8s) secret manager would need an integration with a given application to actually retrieve those secrets - I found this example of injecting secrets from the AWS secret manager service into a running container but it's more up to your application build as the entrypoint script is responsible for retrieving and injecting those secretes into the container environment https://medium.com/@mtreacher/using-aws-kms-for-application-secrets-in-kubernetes-149ffb6b4073 |
Closed by #71 |
It would be nice to see the Hokusai tagging structure created for deploys / promotes
{staging/production}--%yyyy-%mm-%dd--%hh-%MM-%ss
pushed back to the upstream repo on deploy... though this would require CI to have a deploy key with write access.Implement as a flag
--push-git-tags {remote}
that can be added todeploy
/promote
commandsThe text was updated successfully, but these errors were encountered: