fix: create secrets during upgrades (PROJQUAY-7001)

[dmage]

No description provided.

[harishsurf]

lgtm!

[harishsurf]

nit: do we want to replace it with {{ pgdb_password }} defined in secret-vars.yaml

[BadgerOps]

This would probably break existing users postgres DB's, right? If they got swapped from password to an autogenerated password?

I'm not sure how redis handles that change, guessing if its ephemeral it won't cause an issue.

[BadgerOps]

Hey @harishsurf @dmage sorry for this regression - I'm just wrapping up some local testing for a similar PR that generates facts :

- name: Include vars of the config.yaml into the 'quay_config' variable (2.2).
  ansible.builtin.include_vars:
    file: "{{ quay_root }}/quay-config/config.yaml"
    name: quay_config

Then creates the podman secrets with those - the reason I was thinking of going this route is to protect backwards compatibility. Of course, if the better option is to reset the passwords to what is autogenerated in secret-vars.yaml then I'm all for that, and I'll toss my branch 🤣

Edit: Specifically the reason I was considering this route was in case other users had already manually changed the secrets in the config.yaml, and don't want to break their existing installs.

[BadgerOps]

I just submitted #151 with another way - let me know if y'all would prefer to do it another way and I'll close mine!

[dmage]

Replaced by #151.