When configuring Artifactory with system.yaml, the file is overwritten on startup to encrypt the database password. This causes idempotency issues when using orchestration tools for the deployment.
We are migrating to Artifactory 7 and have problems with the configuration. We deploy Artifactory on Docker and have so far used environment variables to set the database configuration. In Artifactory 7 the appropriate way seem to be to configure through system.yaml. Since we use Ansible, we get idempotency issues since the configuration file is overwritten by Artifactory.
Environment variables are still supported in the container entrypoint, but DB_TYPE seems to not affect the database driver correctly (in 7.4.1), thus Artifactory defaults to Derby-driver.
We prefer to use system.yaml, but only if Artifactory uses it read-only. As an alternative we could go back to using environment variables to configure the container, but then DB_TYPE needs to set shared.database.driver correctly.