Andrew Farries
Andrew Farries
## Description Do the necessary plumbing to connect the Stripe webhook (https://github.com/gitpod-io/gitpod/pull/11806) to the `FinalizeInvoice` RPC (https://github.com/gitpod-io/gitpod/pull/11903). With this PR, the webhook calls the `FinalizeInvoice` RPC on the `usage` component...
## Description Allow unknown fields in the `public-api-server` config file. Disallowing unknown fields guards against typos in the config file but makes it harder to deploy config changes independently of...
## Description When Stripe invoices finalize, the webhook is `POST`ed to with an `invoice.finalized` payload indicating the invoice id that was finalized. The exact shape of the payload for each...
## Description Add a trivial 'noop' implementation of `FinalizeInvoice` to the billing RPC service. ## Related Issue(s) Part of #10937 ## How to test * Unit test for the billing...
Ensure that 'alter column' operations that rename a column and also specify `down` SQL (such as those that alter some other column attribute at the time of the rename) must...
When a column is renamed and modified in some other way that requires an `up` and `down` SQL (eg changing its type), migration authors should be able to refer to...
Alter column operations should support specifying fields that are unchanged as no-ops. For example, this migration: ```json { "name": "35_alter_column_multiple", "operations": [ { "alter_column": { "table": "events", "column": "name", "name":...
A way to control the rate at which at backfilling occurs would avoid potential overload on the Postgres instance due to the large amount of I/O that backfilling a large...
Various `pgroll` operations need to duplicate (and backfill) a column on migration start. The general pattern for these operations is: On migration start: * Create a duplicate of the affected...
Migrations are composed of arbitrarily many operations, but with the limitation that a later operation in a migration cannot act on an object that has been created or modified by...