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.

Sign up for GitHub

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

Jump to bottom

Merge Vault and Bao injector tests into one job once OpenBao is stable #428

Open
2 tasks done
csatib02 opened this issue Aug 21, 2024 · 1 comment
Open
2 tasks done

Merge Vault and Bao injector tests into one job once OpenBao is stable #428

csatib02 opened this issue Aug 21, 2024 · 1 comment
Labels
lifecycle/keep Denotes an issue or PR that should be preserved from going stale.

Comments

@csatib02
Copy link
Member

Preflight Checklist

Problem Description

Currently the CI workflow consists of separate jobs for Vault and Bao injectors because Bao injector still has underlying dependencies tied to VAULT env-vars.
Once those are handled, we should be able to run the tests together.

Proposed Solution

Run the tests together once OpenBao is stable, and free of Vault env-var dependencies.

Alternatives Considered

No response

Additional Information

No response
@csatib02
Copy link
Member Author

Tracking: #423

@csatib02 csatib02 changed the title Merge Vault-Bao tets into one job once OpenBao is stable Merge Vault and Bao injector tests into one job once OpenBao is stable Aug 21, 2024
@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR that has become stale and will be auto-closed. label Oct 27, 2024
@csatib02 csatib02 added lifecycle/keep Denotes an issue or PR that should be preserved from going stale. and removed lifecycle/stale Denotes an issue or PR that has become stale and will be auto-closed. labels Oct 27, 2024
@bank-vaults bank-vaults deleted a comment from github-actions bot Oct 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
lifecycle/keep Denotes an issue or PR that should be preserved from going stale.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@csatib02