Meltano UI for containerized project should not allow changes to project files, but can allow changing configuration stored in system database
Right now, we enable the ui.readonly
option in the Dockerfile using the MELTANO_READONLY
environment variable, but really, only actions that touch the project directory itself (meltano.yml
, .meltano/
, .env
etc) need to be blocked.
We may need a new setting, e.g. project.readonly
, which can also be enforced in CLI commands.
Edited by Douwe Maan