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
PostgreSQL state store v2 #2956
Comments
Moving this to P2 for now. Although the issues above are good reasons for a "v2", we are not sure if they're "good enough" by themselves. We may wait a bit on this to see if there's something else that comes up that could require a v2 of the component. CC: @artursouza |
|
There is no timeline. This is not one of our highest priorities right now and there are some decisions we need to carefully make as maintainers. When this is completed YugabyteDB can be added as a separate state store, but until then please wait for this issue to be closed before inquiring further. |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions. |
keep-alive |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions. |
Document how users can inspect the content of a value i.e. this is outlined here |
As we now have "v2" components, we should look into creating a v2 of the Postgres state store to address some long-standing issues:
The text was updated successfully, but these errors were encountered: