Cameronsplaze/AWS-ContainerManager
[Feature] Let the CONFIG_FILE load a URL, on top of the path on disk
Ouverte
#226 ouverte le 21 août 2026
enhancementgood first issue
Métriques du dépôt
- Stars
- (2 étoiles)
- Métriques de merge PR
- (Merge moyen 7j 21h) (4 PRs mergées en 30 j)
Description
Is your feature request related to a problem? Please describe.
The best place is probably around utils.config_loader.load_leaf_config somewhere. Python supports writing to a "temporary" location (we do it in the test suite), so it'd clean up after too.
- Do we just support raw gists, so we can give a clear error if they try to link the "browser" page? We could also just give a clear error on if it fails to load yaml...
- This allows forks to have their custom configs in gists (still version controlled), and not worry about merge conflicts.
- This lets people who pull the project to use directly, to also keep their configs version controlled without having to fork the entire repo.
- Since in GH Actions, the container-id=environment-name, it doesn't matter what the file-name is. The environment-name will control what the URL/Stack-ID becomes.
Describe the solution you'd like
Above...
Describe alternatives you've considered
Above...
Acknowledgements
- I may be able to implement this feature request
- This feature might incur a breaking change