nebari
nebari copied to clipboard
[ENH] Move Vault secrets and provider auth to custom action
Reference Issues or PRs
What does this implement/fix?
Put a x in the boxes that apply
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds a feature)
- [ ] Breaking change (fix or feature that would cause existing features not to work as expected)
- [ ] Documentation Update
- [ ] Code style update (formatting, renaming)
- [ ] Refactoring (no functional changes, no API changes)
- [ ] Build related changes
- [ ] Other (please describe):
Testing
- [ ] Did you test the pull request locally?
- [ ] Did you add new tests?
How to test this PR?
Any other comments?
@viniciusdc is this ready for review? Is there an associated issue?
@viniciusdc with Vault failing relatively frequently, I'm wondering if we should consider just using GitHub secrets instead. Any thoughts?
C.C. @Adam-D-Lewis @dcmcand
I would be in favor of moving away from vault
I opened https://github.com/nebari-dev/nebari/issues/2835
We're going to address https://github.com/nebari-dev/nebari/issues/2835 so we won't be merging this PR