This will allow us to not need to deploy a config file on containers, and depend less on the filesystem.
For example, when starting a webservice shell.
This will allow us to not need to deploy a config file on containers, and depend less on the filesystem.
For example, when starting a webservice shell.
We can start only with the toolforge api url, so we unblock the move out of the old bastion, and then move the whole config to use pydantic-settings
dcaro opened https://gitlab.wikimedia.org/repos/cloud/toolforge/toolforge-weld/-/merge_requests/66
config: load api url from env too
dcaro merged https://gitlab.wikimedia.org/repos/cloud/toolforge/toolforge-weld/-/merge_requests/66
config: load api url from env too
raymond-ndibe opened https://gitlab.wikimedia.org/repos/cloud/toolforge/toolforge-weld/-/merge_requests/68
d/changelog: bump to 1.6.5
raymond-ndibe merged https://gitlab.wikimedia.org/repos/cloud/toolforge/toolforge-weld/-/merge_requests/68
d/changelog: bump to 1.6.5