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

Backwards compatibility support #18

Open
ramizpolic opened this issue Nov 9, 2023 · 1 comment · Fixed by #35
Open

Backwards compatibility support #18

ramizpolic opened this issue Nov 9, 2023 · 1 comment · Fixed by #35
Assignees
Labels
area/provider/vault kind/design Categorizes issue or PR as related to design. lifecycle/keep Denotes an issue or PR that should be preserved from going stale. priority/longterm Important over the long term, but may not be worked in multiple releases

Comments

@ramizpolic
Copy link
Member

ramizpolic commented Nov 9, 2023

Overview

  • What are the challenges for supporting backwards compatibility with vault-env?
  • How do we want to approach this problem?
  • Is it something we need to address as soon as possible or can we continue with the development?

Note: This are just some general questions to have in mind going forward. Feel free to add more context to it so we can keep track and discuss possible solutions.

@csatib02 csatib02 linked a pull request Dec 15, 2023 that will close this issue
This was referenced Dec 15, 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 Jan 14, 2024
@ramizpolic ramizpolic removed question lifecycle/stale Denotes an issue or PR that has become stale and will be auto-closed. labels Jan 23, 2024
@ramizpolic ramizpolic reopened this Jan 25, 2024
@ramizpolic
Copy link
Member Author

This is still relevant to keep track of changes for integration options

@ramizpolic ramizpolic added the lifecycle/keep Denotes an issue or PR that should be preserved from going stale. label Jan 25, 2024
@csatib02 csatib02 added kind/design Categorizes issue or PR as related to design. area/provider/vault priority/longterm Important over the long term, but may not be worked in multiple releases labels Apr 30, 2024
@csatib02 csatib02 self-assigned this Apr 30, 2024
@bank-vaults bank-vaults deleted a comment from github-actions bot Jul 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/provider/vault kind/design Categorizes issue or PR as related to design. lifecycle/keep Denotes an issue or PR that should be preserved from going stale. priority/longterm Important over the long term, but may not be worked in multiple releases
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants