You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@arrow.apache.org by "nyurik (via GitHub)" <gi...@apache.org> on 2025/10/14 22:07:43 UTC

[I] Introduce common configuration patterns for file/CLI/env-var usage [arrow-rs-object-store]

nyurik opened a new issue, #507:
URL: https://github.com/apache/arrow-rs-object-store/issues/507

   **Is your feature request related to a problem or challenge? Please describe what you are trying to do.**
   
   Most users of this great crate will usually allow their users to configure bucket access. This includes things like bucket name, region, tokens or automatic environment variable parsing, and lots and lots of other aspects.  Most of the users of this crate will not even be aware of the various configuration options available, nor do they want to be.  Yet, if they get it wrong, some end users who need a very specific authentication mode or other non-so-common setup will suffer. This lib supports it, they know about it, but the specific app that uses this crate is not passing through the right config.
   
   **Describe the solution you'd like**
   
   Introduce a set of reusable components targeting all 3 usecases:
   * configuration files - some serde-instrumented structs/enums that can parse yaml/toml/json files in the same way to allow any needed configuration
   * CLI - clap-instrumented structs for the same
   * env vars - this one seem to be mostly done - but would be good if it works well with the other two methods
   
   **Describe alternatives you've considered**
   Each user of this lib implement it by hand
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Introduce common configuration patterns for file/CLI/env-var usage [arrow-rs-object-store]

Posted by "kylebarron (via GitHub)" <gi...@apache.org>.
kylebarron commented on issue #507:
URL: https://github.com/apache/arrow-rs-object-store/issues/507#issuecomment-3430279791

   I would love for the documentation of the Rust crate to be better, but it's unclear to me how that relates to downstream projects. Would you expect consumers of your library to need to reference the Rust docs on `docs.rs/object-store` of this project?
   
   For context, I also have fully duplicated the documentation into my Python bindings: https://developmentseed.org/obstore/latest/api/store/aws/#obstore.store.S3Config


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Introduce common configuration patterns for file/CLI/env-var usage [arrow-rs-object-store]

Posted by "CommanderStorm (via GitHub)" <gi...@apache.org>.
CommanderStorm commented on issue #507:
URL: https://github.com/apache/arrow-rs-object-store/issues/507#issuecomment-3429998666

   ALso the documentation problem.
   Currently, every consumer of the config needs to essentially do this work (click on S3 😉):
   
   https://maplibre.org/martin/sources-files.html#serving-pmtiles-from-local-file-systems-http-or-object-storage
   
   I would be more than willing to help out documenting this, if I can get buy in from project mantainers for the rough "how" and "where" first.
   
   Related:
   - https://github.com/apache/arrow-rs-object-store/pull/498


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org