[usage] Make billing optional in the usage component

[andrew-farries]

Description

Make the payment processing part of the usage controller optional. If the secret containing Stripe API keys is configured then enable payments, otherwise disable it.

Usage metering and usage based billing are separate concepts that we will need to enable and disable independently of one another. In Gitpod SaaS we will want both, but for self-hosted installations, users will only care about usage metering.

At some point we will want to have the usage collection and billing integration in separate services but for now, while they both live in the usage component, let's at least be able to toggle billing integration on and off.

Related Issue(s)

Part of #9036

How to test

• Trigger separate Werft builds, one setting with-payment=true and the other without.
• Observe that when payment is enabled, the usage component runs with billing integration enabled:

  {"level":"info","message":"payment integration with Stripe is set to true","serviceContext":{"service":"usage","version":"commit-b5ca1b4eebb51424345134f6847f9d180bd7c44f"},"severity":"INFO","time":"2022-06-20T05:56:38Z"}
  

  and when payment is not enabled, observe that it runs with billing integration disabled:

  {"level":"info","message":"payment integration with Stripe is set to false","serviceContext":{"service":"usage","version":"commit-b5ca1b4eebb51424345134f6847f9d180bd7c44f"},"severity":"INFO","time":"2022-06-20T05:56:38Z"}
  

Release Notes

NONE

Documentation

None

[andrew-farries]

/hold

[andrew-farries]

/werft run

👍 started the job as gitpod-build-af-usage-make-payment-integration-optional.25
(with .werft/ from main)

[easyCZ]

LGTM % comments (up to you to address, if you think they are valid)

/hold

[andrew-farries]

/werft run with-clean-slate-deployment=true

👍 started the job as gitpod-build-af-usage-make-payment-integration-optional.27
(with .werft/ from main)

[andrew-farries]

I'm not sure why Werft is failing here 😕 .

There are no obvious error message in the logs. The last line of the output is:

[components/usage:app] === RUN   TestListWorkspaceInstancesInRange_InBatches

[easyCZ]

I'm not sure why Werft is failing here 😕 .

There are no obvious error message in the logs. The last line of the output is:

[components/usage:app] === RUN   TestListWorkspaceInstancesInRange_InBatches

That test may output a rather long log line. It's possible it doesn't sit well with werft. Main (which contains the same test) is happy however.

[andrew-farries]

We should probably not run the tests for the usage component in verbose mode as they are very noisy.

[andrew-farries]

This looks to be more widespread than just this branch.

https://werft.gitpod-dev.com/job/gitpod-build-af-add-timeout-show-command.8/raw now also failing at the same point.

[easyCZ]

Fix for the debug logging in #10815

[easyCZ]

@gitpod-io/engineering-self-hosted Would you be able to please help review this?

[corneliusludmann]

Went over the code and it looks good so far. Since we do not own code that is touched in this PR, let me know if you need me to review something in particular.

[andrew-farries]

/unhold