-
Notifications
You must be signed in to change notification settings - Fork 165
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
multiple backends > display improvements #224
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Indeed, I don't think there is a way to distinguish the sources in the GUI. It'd definitely be an interesting feature, for which we'd welcome a PR. |
We could definitely make use of this feature, as our org has more than 6 distinct accounts sharing primary bucket path. If anyone has thoughts on making a switchable front page based on account selection triggered by SSO login, I'd be willing to contribute. |
I have achieved multiple backends from the same provider but different accounts, like staging backend and development backend. Successfully able to pull the data from these backends on the tarraboard UI. but Im looking forward to achieve for differentiation those backends on the UI part. feel free to help me out on this blocker. thanks! |
I too could use this, I've even gone as far as to query the DB directly and haven't found how we track the backend of each state |
I really love the feature that you now can have multiple backends (s3 buckets in our case).
Though while testing this I noticed that in the GUI there is no way to distinct which resource is defined in which backend.
This especially becomes a problem if the paths are looking alike.
Am I overseeing a configuration option to enable this in the GUI?
The text was updated successfully, but these errors were encountered: