set user for visibility db in VISIBILITY_DBUSER env var #163
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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