feat(providers): add minio (mc) and stui endpoint providers - #1
Closed
leduckhc wants to merge 1 commit into
Closed
Conversation
Resolve a connection target across three independent config sources with no cross-provider fallback: - aws: ~/.aws/config (+ credentials), SSO - minio: ~/.mc/config.json aliases (honors $MC_CONFIG_DIR) - stui: ~/.config/stui/config.json endpoints (with optional static creds) A profile/alias name is matched within a single provider; an ambiguous name errors and asks for --provider. Adds --alias and --provider flags, custom S3 endpoint + path-style + static-credential support on the client, and surfaces per-provider load errors instead of silently dropping them.
Owner
Author
|
Superseded by upstream PR natevick#1 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Resolve a connection target across three independent config sources with
no cross-provider fallback:
A profile/alias name is matched within a single provider; an ambiguous name
errors and asks for --provider. Adds --alias and --provider flags, custom S3
endpoint + path-style + static-credential support on the client, and surfaces
per-provider load errors instead of silently dropping them.