Allow the Clusterpedia DB user/role to not own the resource table

[TNonet]

What would you like to be added?

Allow the Clusterpedia DB user/role to check the schema of the resource table and throw errors if the schema is wrong rather than adjust the table itself.

This would mean that the Clusterpedia DB user/role would not require ownership over the resource table

Why is this needed?

Requiring the Clusterpedia DB user/role to own the resource table can make migrations/maintenance difficult.

[clusterpedia-bot]

Hi @TNonet,
Thanks for opening an issue!
We will look into it as soon as possible.

Details

Instructions for interacting with me using comments are available here.
If you have questions or suggestions related to my behavior, please file an issue against the gh-ci-bot repository.

[Iceber]

Hi @TNonet, After the first launch and once the database has finished initializing, you can switch to a lower-privileged user. This way, even if a newer version of the code triggers an automatic migrate later, the update will fail due to insufficient permissions.

BTW, would you like the SQL schema files to handle manual creation or upgrades?

[TNonet]

Hi @Iceber ,

Thanks for the response. I have a few comments / questions.

After the first launch and once the database has finished initializing, you can switch to a lower-privileged user.

Are you open to allowing the user to always be lower-privileged and just fail if the schema is incompatible or is this the best alternative atm?

BTW, would you like the SQL schema files to handle manual creation or upgrades?

I am not sure I follow what you mean here. Can you expand?

I would ideally like to prevent any major bump in the Clusterpedia table schemas so any schema changes needed are backward/forwards compatible and could be rolled out separately of the Clusterpedia upgrade itself. For example the timing could look like this:

1. Upgrade the Clusterpedia table to schema version X+1
   • This would only be non-breaking (nullalbe) column additions
2. Upgrade the Clusterpedia services to package version N+1 (which uses schema version X+1)
3. [Optional] Upgrade the schema version to X+2 (which could remove the nullability of the new columns)