This message was deleted.
# awss
sparse-intern-71089
07/21/2021, 12:25 AMThis message was deleted.
b
bored-table-20691
07/21/2021, 12:31 AMTypically the way I’ve seen this done (e.g. with a normal Aurora cluster, which I don’t think is different in this regard) is one of two ways:
1. Use the Automation API to run your stack to create the username in Aurora (you’d do this using the Postgres provider)
2. Create the Aurora cluster in one project/stack, and reference it in another stack and create the user there.
That said, typing this out, is there a reason you can’t just use the Postgres provider (or MySQL or whatever it is you’re using with Aurora) and construct it with the Aurora details?
c
colossal-ice-49128
07/21/2021, 2:24 AMI tried doing that but I ran into this error which made me think I was going in the wrong direction. I’ll try the suggested fix in that thread (although that’s for terraform and may be difficult to apply to Pulumi).
b
bored-table-20691
07/21/2021, 2:36 AMWhat does the code roughly look like
c
colossal-ice-49128
07/21/2021, 2:43 AM Copy code
const role = new postgres.Role("role", {
login: true,
name: "role",
password: 'password'
})
const grant = new postgres.Grant("halo-application-grant", {
database: theCluster.databaseName,
objectType: "database",
privileges: ["SELECT", "INSERT", "UPDATE", "DELETE"],
role: role.name,
})colossal-ice-49128
07/21/2021, 2:43 AMthat’s what’s causing the error, I’m looking at how to set the provider option
superuser = falsecolossal-ice-49128
07/21/2021, 3:03 AMok, making progress on this. I added
postgresql:superuser: falsecolossal-ice-49128
07/21/2021, 3:33 AMok, got that working, thanks.
b
bored-table-20691
07/21/2021, 3:46 AMCool. I think generally Pulumi knows to wait until the cluster is done
6 Views