Can't install onto RDS about supermarket-omnibus-cookbook HOT 5 OPEN

Thanks for reporting that @boydj ! Would you mind submitting a PR to re-add those lines?

from supermarket-omnibus-cookbook.

I think if these lines were to go somewhere, they would be in the omnibus-supermarket recipe that is internal to the omnibus package. I propose that this issue move to the chef/supermarket repo under the guise of "handle PG database ownership and enabling PG extensions when PG is run external to the omnibus install." The solution might be something other than flipping these resources off if omnibus'd-postgresql is disabled. For example, I can picture adding to the database recipe a .pgpass file for psql commands to pick up and use to authenticate to wherever PG is running during these configuration steps.

from supermarket-omnibus-cookbook.

Looking a bit closer at the error, the specific error has to do with the expectation that the execute resource for the psql command will be run with an OS user that matches the name of a user within the PostgreSQL service who has the privileges to install extensions. This is true for the default install—supermarket OS service account and supermarket PG database user—but not necessarily true for a PG database configured elsewhere. In @boydj's case, there is a chef user in the RDS database, but that an OS user of the same name does not exist on the Supermarket host (and also maybe shouldn't).

I sense that the bug here is assuming that an OS user for the command to install extensions will match an admin DB user. We should spend a little time unpacking that.

from supermarket-omnibus-cookbook.

I can confirm that changing the DB user to match a system user, in this case, supermarket, allows installation to complete successfully.

from supermarket-omnibus-cookbook.

Thanks for the confirmation, @boydj. That helps shape our options. I see them as:

• document the current expectation—requirement, really—that the database username match the OS service account name, defaulted to supermarket (increased cognitive load on the humans performing an install)
• update the omnibus package's internal cookbook to provide the flexibility to private Supermarkets to pick the name of the database user (increased code complexity)

Are those reasonable? Are there others?

from supermarket-omnibus-cookbook.