Quite minor issue, though still adding it here for future reference. As the title says, running verdi presto --use-postgres specifying an already existing profile still creates the PSQL db, and only afterwards fails during profile creation:
❯ verdi presto --profile-name 'psql-presto' --use-postgres
Report: `--use-postgres` enabled and database creation successful: configuring the profile to use PostgreSQL.
Report: RabbitMQ server detected: configuring the profile with a broker.
Report: Initialising the storage backend.
Report: Storage initialisation completed.
Success: Created new profile `psql-presto`.
Success: Configured the localhost as a computer.
❯ verdi presto --profile-name 'psql-presto' --use-postgres
Warning: Database "aiida-psql-presto" already exists.
Report: `--use-postgres` enabled and database creation successful: configuring the profile to use PostgreSQL.
Report: RabbitMQ server detected: configuring the profile with a broker.
Critical: The profile `psql-presto` already exists.
Quite minor issue, though still adding it here for future reference. As the title says, running
verdi presto --use-postgres
specifying an already existing profile still creates the PSQL db, and only afterwards fails during profile creation:leading to:
I think it would be nicer if it wouldn't create the db, if the profile already exists, as well as a db with the same name.