Use existing secret rework

[mrdotb]

What this PR does / why we need it:

Use existing secret.

Changes:

I added the ability to bring an existing secrets that we discussed in #3.

I separated the values related to postgres and clickhouse optional deps to be first level databaseURL, clickhouseDatabaseURL
We can discuss this but I feel like it's confusing to access values from deps that are not supported in their chart and if you want to bring your own postgres or clickhouse it make more sense.

I got ride of the secrets postgres and clickhouse password ... that are only used in the init containers and replaced that by parsing the DB URL in scripts instead. I also moved the init container check on first level for the same reasons as before.
I also got ride of the clickhouse curl check not sure why two scripts are needed ?

I updated the plausible ENV some where removed some where added. (twitter, adminUser, mailer ...)

The chart version need to be bumped but I will do that after the review.

There is an issue with the CI does not seem related with my changes ERROR: Unable to validate cosign version: 'v2.0.0'

Checklist

[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

• DCO signed
• Chart Version bumped
• Variables are documented in the README.md

[alexnuttinck]

Hi @mrdotb,

Thanks a lot for your contribution and the refactoring about the environment variables and the init scripts!
Could you have a check about my 2 comments before we can merge?

I also got ride of the clickhouse curl check not sure why two scripts are needed ?

I added this init check because we use an external clickhouse where the port 9000 is not opened. But I agree there is no sense to have 2 methods to verify that clickhouse is ready.

The chart version need to be bumped but I will do that after the review.
I will bump it to 0.2.0 as a lot of default variables have changed.

There is an issue with the CI does not seem related with my changes ERROR: Unable to validate cosign version: 'v2.0.0'

I will have a look. It seems to be related to this isuue.

[alexnuttinck]

@mrdotb I think we should be able to set the SMTP_USER_PWD for any mailer adapters.

[mrdotb]

Why for ?
The https://hexdocs.pm/bamboo_smtp/Bamboo.SMTPAdapter.html use smtp but all the others rely on third party API that only need an api key except mailgun.
The only common things to mailer are the email which is the sender.
My update on mailer values reflect that.

mailer:
  enabled: false  # Enable/Disable functionality
  email: ""  # the email address of the email sender
  adapter: ""  # "Bamboo.SMTPAdapter", "Bamboo.MailgunAdapter", "Bamboo.MandrillAdapter", "Bamboo.SendGridAdapter"
  smtp:
    host: ""  # The host address of your smtp server.
    port: ""  # The port of your smtp server.
    username: ""  # The username/email in case SMTP auth is enabled.
    password: ""  # The password in case SMTP auth is enabled.
    ssl: ""  # If SSL is enabled for SMTP connection
    retries: ""  # Number of retries to make until mailer gives up.
  mailgun:
    apiKey: ""
    domain: ""
    baseURI: ""
  postmarkApiKey: ""
  mandrillApiKey: ""
  sendgridApiKey: ""

Did I miss something ?

[mrdotb]

https://github.com/pablo-co/bamboo_postmark for reference only require the postmarkApiKey

[alexnuttinck]

@mrdotb Nope sorry, I misunderstood when I read the docs from plausible. Thanks for the link, you are right! Let's merge 🚀

[alexnuttinck]

@mrdotb the same here, I think we should be able to set the SMTP_HOST_ADDR for any mailer adapters.