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

Enable syncing from multiple stores #85

Open
ramizpolic opened this issue Nov 15, 2023 · 0 comments
Open

Enable syncing from multiple stores #85

ramizpolic opened this issue Nov 15, 2023 · 0 comments
Labels
lifecycle/keep Denotes an issue or PR that should be preserved from going stale. priority/low Issue that might be added to backlog or be rejected.
Milestone
future

Comments

@ramizpolic
Copy link
Member

Overview

We would like to be able to synchronize secrets from multiple different secret stores (e.g. Vault + AWS + GCP) into a single selected destination store (e.g. Vault).
@ramizpolic ramizpolic self-assigned this Nov 16, 2023
@ramizpolic ramizpolic changed the title Feature: Enable syncing from multiple stores Enable syncing from multiple stores Nov 16, 2023
@ramizpolic ramizpolic added lifecycle/keep Denotes an issue or PR that should be preserved from going stale. and removed lifecycle/keep Denotes an issue or PR that should be preserved from going stale. labels Dec 4, 2023
@ramizpolic ramizpolic added this to the v0.2.0 milestone Dec 8, 2023
@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR that has become stale and will be auto-closed. label Feb 11, 2024
@ramizpolic ramizpolic removed the lifecycle/stale Denotes an issue or PR that has become stale and will be auto-closed. label Feb 12, 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 Apr 14, 2024
@csatib02 csatib02 removed the lifecycle/stale Denotes an issue or PR that has become stale and will be auto-closed. label Apr 14, 2024
@ramizpolic ramizpolic removed their assignment Jun 11, 2024
@ramizpolic ramizpolic added the priority/low Issue that might be added to backlog or be rejected. label Jun 11, 2024
@ramizpolic ramizpolic modified the milestones: v0.2.0, future Jun 11, 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 Aug 11, 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 Aug 11, 2024
@bank-vaults bank-vaults deleted a comment from github-actions bot Aug 11, 2024
@bank-vaults bank-vaults deleted a comment from github-actions bot Aug 11, 2024
@bank-vaults bank-vaults deleted a comment from github-actions bot Aug 11, 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. priority/low Issue that might be added to backlog or be rejected.
Projects
None yet
Milestone
future
Development

No branches or pull requests
2 participants
@ramizpolic @csatib02