You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The UI needs to be able to know some more details when the tenant is using external payment. Right now that covers both people handling manual billing/contracts and when using a 3rd party marketplace like Google or AWS. We can figure out if Google is used with the gcm_account_id column.. However, for anything else we do not really know.
We should expand the public.payment_provider_type type to allow for some more detail beyond external. Potentially we add all the payment providers we support there?
The enum would become something like... 'stripe', 'external', 'gcp', 'aws'
I think this might mean extra work for billing/invoicing/etc. because then we might need more handled than just is 'external'
Second Idea
We add a new column to the tenant table that stores something we need for aws in a new column. This would probably be something similar to how we do it for Google where we store their account id.
The text was updated successfully, but these errors were encountered:
Background
The UI needs to be able to know some more details when the tenant is using
external
payment. Right now that covers both people handling manual billing/contracts and when using a 3rd party marketplace like Google or AWS. We can figure out if Google is used with thegcm_account_id
column.. However, for anything else we do not really know.Split off from: estuary/ui#1443
Request
I think we could have two simple choices
First Idea
We should expand the
public.payment_provider_type
type to allow for some more detail beyondexternal
. Potentially we add all the payment providers we support there?The enum would become something like...
'stripe', 'external', 'gcp', 'aws'
I think this might mean extra work for billing/invoicing/etc. because then we might need more handled than just
is 'external'
Second Idea
We add a new column to the
tenant
table that stores something we need foraws
in a new column. This would probably be something similar to how we do it for Google where we store their account id.The text was updated successfully, but these errors were encountered: