The Python CLI for maintaining a Gicha stack... or dozens of them!
pip install gicha
python -m gicha --help
python -m gicha --app-name=gicha-base
Those configurations will be automatically saved in gicha.yml at the end of the creation.
pip install gicha --upgrade
python -m gicha --app-name=gicha-base --output-dir=folder-already-created
Note the --upgrade
and the --output-dir=folder-already-created
flags. The Gicha configuration that was used for the previous generation is saved in gicha.yml
: it will be updated after the new upgrade.
If you want to do an upgrade without re-specifying each parameter (there are a lot of them!), then gicha conveniently provides de --gicha-conf
parameter.
Just modify the existing gicha.yml
(modify mandatorily the version
parameter so that it reflects the newly upgraded version,
modify optionally any other parameter depending on your needs), then:
pip install gicha --upgrade
cd folder-already-created
python -m gicha --gicha-conf=gicha.yml --output-dir=.
If your calls last longer than 30 seconds (but less than 15 minutes), then you need to do the invocations through Function URL.
- Call Gicha
--with-function-url=true
. This will just save the configuration ingicha.yml
for now. You need to additionally perform the following two instructions. - Activate Function URL. You can use either AWS Console or CLI.
- Set handler to
app.minimalistic_handler
. You can use either AWS Console or CLI.
- TODO: automate step 2 and 3
- When calls are done through Function URL,
- then Chalice routing with @app.route does __NOT__ work:
- route manually!