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

set user for visibility db in VISIBILITY_DBUSER env var #163

Merged
merged 4 commits into from
Mar 22, 2024

Conversation

avimoondra
Copy link
Contributor

@avimoondra avimoondra commented Mar 22, 2024

Support using different users, each scoped to the DB (default store, visibility store) they are expected to manage. in our auto set up scripts (https://github.com/tryretool/retool-temporal-docker-builds/pull/2) we assume the same user is used to set up schema for both these databases.

see issue here: https://retooled.slack.com/archives/C05TR7RRB0F/p1710327058225469

relates to https://github.com/tryretool/retool-temporal-docker-builds/pull/2

@avimoondra avimoondra marked this pull request as ready for review March 22, 2024 14:50
@avimoondra avimoondra force-pushed the avimoondra/introduce-a-db-visibility-user branch from 551fee2 to 35ed7d7 Compare March 22, 2024 14:51
@@ -25,7 +25,7 @@ server:
autosetup: true
image:
repository: tryretool/one-offs
tag: retool-temporal-1.1.3
tag: retool-temporal-1.1.5
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the main change, rest is formatting

@avimoondra avimoondra merged commit 8c114c8 into main Mar 22, 2024
12 checks passed
@avimoondra avimoondra deleted the avimoondra/introduce-a-db-visibility-user branch March 22, 2024 18:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants