remote_config
| Crates.io | remote_config |
| lib.rs | remote_config |
| version | 0.2.0 |
| source | src |
| created_at | 2024-06-25 10:41:39.885679 |
| updated_at | 2024-06-26 20:58:23.349865 |
| description | Flexible crate for asynchronously loading configuration from remote source with caching and automatic revalidation. |
| homepage | |
| repository | https://github.com/CaptainDno/remote-config |
| max_upload_size | |
| id | 1283223 |
| size | 49,853 |
Sergey (CaptainDno)
documentation
README
Remote config
This crate provides easy way to asynchronously pull configuration files from external source (e.g. centralized HTTP service).
It was originally developed to load public keys from https://www.googleapis.com/robot/v1/metadata/x509/securetoken@system.gserviceaccount.com
and revalidate them periodically.
Features
- Supports both
staticand wrapped inArcconfigs. - Flexible
RemoteConfigstruct that uses any custom data provider and automatically revalidates data when it becomes stale. - Supports loading configuration in JSON, YAML, XML and TOML via HTTP out of the box (Uses
Cache-ControlandContent-Typeheaders).
Documentation and examples
Refer to documentation and examples on docs rs.
State of the project
Project is not guaranteed to actively receive any new features without requests, but is maintained. Feature requests, bug reports, pull requests, corrections to docs or examples are gladly accepted.
Code is tested, with unit and integration tests.
Currently, this project is not used in production environment.
Contributing
If you found a bug, submit an issue or pull requests.
Any contribution intentionally submitted for inclusion in Tokio by you, shall be licensed as MIT, without any additional terms or conditions.
Licence
This project is licenced under the MIT licence.