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

chore: Revert "Merge pull request #513 from carnei-ro/feat/bitwarden-secrets… #515

Merged
merged 1 commit into from
Sep 7, 2024

Conversation

zhaque44
Copy link
Contributor

@zhaque44 zhaque44 commented Sep 7, 2024

resolved: #514

reverting adding the bitwarden secrets provider, our plan is to enhance our CI pipeline with more robust testing and then add it the provider back with minimal changes not with musl-gcc <-

…-secrets-manager"

This reverts commit 5378cfa, reversing
changes made to 35d76ca.

Signed-off-by: zhaque44 <haque.zubair@gmail.com>
@zhaque44 zhaque44 force-pushed the rm-bitwarden-secrets branch from e78b634 to 703242f Compare September 7, 2024 11:53
@yxxhero yxxhero merged commit 4e977c5 into helmfile:main Sep 7, 2024
4 checks passed
@carnei-ro
Copy link
Contributor

I said here that the Bitwarden Secrets would need CGO enabled and musl-gcc #427 (comment)

@zhaque44
Copy link
Contributor Author

zhaque44 commented Sep 7, 2024

I said here that the Bitwarden Secrets would need CGO enabled and musl-gcc #427 (comment)

We didn’t want any of the third party stuff you bought in like musl-gcc or anything like that. We will be enhancing our CI, and then trying to add that bitwarden after that

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

Successfully merging this pull request may close these issues.

The release v0.37.4 failed
3 participants