vs-starter merge requestshttps://gitlab.eox.at/vs/vs-starter/-/merge_requests2022-01-18T17:12:56+01:00https://gitlab.eox.at/vs/vs-starter/-/merge_requests/1Remove base and logging conf from vs-starter2022-01-18T17:12:56+01:00Bernhard MallingerRemove base and logging conf from vs-starterThis config can be static in actual deployment, so we don't need to
generate itThis config can be static in actual deployment, so we don't need to
generate ithttps://gitlab.eox.at/vs/vs-starter/-/merge_requests/2Dem app deploy2022-02-11T16:16:02+01:00Lubomir DoležalDem app deploy- adds `dem-app` deployment config https://gitlab.eox.at/esa/prism/dem-app
- adds `ENABLE_HTTP_ACCESS` to both registrar and renderer, as both can initiate stack
- enable HTTP_ACCESS for all slugs- adds `dem-app` deployment config https://gitlab.eox.at/esa/prism/dem-app
- adds `ENABLE_HTTP_ACCESS` to both registrar and renderer, as both can initiate stack
- enable HTTP_ACCESS for all slugshttps://gitlab.eox.at/vs/vs-starter/-/merge_requests/3MAZSIZE to MAXSIZE2022-04-27T15:47:56+02:00Lubomir DoležalMAZSIZE to MAXSIZEonhold until new vs/core releaseonhold until new vs/core releaseLubomir DoležalLubomir Doležalhttps://gitlab.eox.at/vs/vs-starter/-/merge_requests/4replace concept of extra-values-file with a new per-instance override2022-11-07T15:32:14+01:00Lubomir Doležalreplace concept of extra-values-file with a new per-instance overrideMain feature: prism specific configurations, labels and secrets were removed (moved to `esa/prism/config-values`).
Parameter `--extra-parameter-file` replaced with multiple `-o/--instance-override` override switches which need an absolu...Main feature: prism specific configurations, labels and secrets were removed (moved to `esa/prism/config-values`).
Parameter `--extra-parameter-file` replaced with multiple `-o/--instance-override` override switches which need an absolute path.
The argument is handled as another jinja template rendered with the available env variables and other (same way as before). This helps to split the final docker compose composition into:
- `docker-compose.yml` - contains base service configurations that are likely not going to change (so is placed in `vs-starter/templates`)
- `docker-compose.shared.yml` - contains overrides for specific platform (staging/dev/ops) but with configurations more or less same for each stack that gets created. This was previously the `docker-compose.instance.yml`!
- `docker-compose.instance.yml` - contains collection specific overrides, additional services etc.
both `docker-compose.shared.yml` and `docker-compose.instance.yml` are supplied (handcrafted) by the operator
Deployment would then look like:
`slug=vhr15 && docker stack deploy -c "$slug"/docker-compose.yml -c "$slug"/docker-compose.shared.yml -c "$slug"/docker-compose.instance.yml "$slug"`
Additionally:
- store showcase (basic working traefik) docker compose overrides in sample_templates/
- extract more variables from rendered helm templates
- add general python package misc things - dev requirements, ci part of linting, docs, bump version config etc.https://gitlab.eox.at/vs/vs-starter/-/merge_requests/5Vs unified chart2023-06-12T08:50:54+02:00Lubomir DoležalVs unified chart