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

vault-configurer periodic checks #654

Open
2 tasks done
paraddise opened this issue Oct 1, 2024 · 2 comments
Open
2 tasks done

vault-configurer periodic checks #654

paraddise opened this issue Oct 1, 2024 · 2 comments
Labels
kind/enhancement Categorizes issue or PR as related to an improvement.

Comments

@paraddise
Copy link

Preflight Checklist

  • I have searched the issue tracker for an issue that matches the one I want to file, without success.
  • I agree to follow the Code of Conduct.

Problem Description

Sometimes state of the Vault changes manually by user. And state become inconsistent until vault-configurer restarted.

Proposed Solution

Make vault-configurer periodically fetch state from Vault and sync it.

Alternatives Considered

Of course I can periodically (e.g. 1 min) restart pod with vault-configurer.

Additional Information

That would be 1 more step to making full vault gitops management.
@paraddise paraddise added the kind/enhancement Categorizes issue or PR as related to an improvement. label Oct 1, 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 Dec 1, 2024
@csatib02 csatib02 transferred this issue from bank-vaults/bank-vaults Dec 1, 2024
@csatib02 csatib02 removed the lifecycle/stale Denotes an issue or PR that has become stale and will be auto-closed. label Dec 1, 2024
@bank-vaults bank-vaults deleted a comment from github-actions bot Dec 1, 2024
@github-actions GitHub Actions
Copy link

github-actions bot commented Feb 2, 2025

Thank you for your contribution! This issue has been automatically marked as stale because it has no recent activity in the last 60 days. It will be closed in 20 days, if no further activity occurs. If this issue is still relevant, please leave a comment to let us know, and the stale label will be automatically removed.

@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 2, 2025
@paraddise
Copy link
Author

Still wait for implementation

@github-actions github-actions bot removed the lifecycle/stale Denotes an issue or PR that has become stale and will be auto-closed. label Feb 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/enhancement Categorizes issue or PR as related to an improvement.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@paraddise @csatib02