feat: add parameters to allow migrate job to use its own database account and service account#98
Conversation
c4d1bd5 to
b71ac60
Compare
|
Interesting... the Contribution Guidelines say the CLA is required, but don't also mention DCO (which seems belt & suspenders to me). |
…ount and service account Signed-off-by: Evan Anderson <evan@stacklok.com>
b71ac60 to
471639f
Compare
|
I'm not sure how this is supposed to be tested. I did some manual testing, but didn't see any testing directions. |
Signed-off-by: Evan Anderson <evan@stacklok.com>
|
I updated the |
|
@evankanderson thanks for the contribution! Do you mind doing a screen capture of this working in action? That will help me manually verify it a little better and it could help future eyes landing on this to know how to use it a little better. |
Apologies for the confusion - we just disabled the DCO, it was from the time the CLA was not enabled on this repo. Thanks for pointing it out! |
Fixes #95
Description
Add parameters to enable running the migration job with a different database access level.
PGPASSFILEfile with credentials (which rotate every 15 minutes).PGPASSFILEin the migration containerReferences
(Unfortunately, our other examples of doing this aren't public)
Review Checklist
main