Skip to content
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

The latest release does not include a secret-agent.yaml which causes the install of secret agent from forgeops to fail. #239

Open
RobinVanhove opened this issue Jun 2, 2023 · 4 comments
Assignees

Comments

@RobinVanhove
Copy link

Previous releases included a 'secret-agent.yaml' file, but the latest release v1.1.9 does not include this file.

The script to install the secret agent from the ForgeOps repo depends on this file.

Is there a reason why this file is not added?

@lee-baines lee-baines self-assigned this Mar 13, 2024
@lee-baines
Copy link
Contributor

Hi, apologies for not responding sooner. This is usually provisioned as part of the release process. The latest versions include a secret-agent.yaml file. Please install the latest version which is v1.2.2 which includes the latest security patches

@balpurewal
Copy link

Hi @lee-baines, where is the latest release v1.2.2? I can pull the image from us-docker.pkg.dev/forgeops-public/images/secret-agent:v1.2.2 but can't see the release artifacts. Thanks

@lee-baines
Copy link
Contributor

Hi @balpurewal, we had to pull the v1.2.2 release due to some issues with secret backups. We've been working on the bugs and should be able to rerelease v1.2.2 soon. We kept the docker image there so it didn't break for customers who had already deployed v1.2.2 and restarting the pod would pull the image again.

@balpurewal
Copy link

Thanks @lee-baines

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants