-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[usage] Configure Stripe Price IDs through installer #14124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -167,6 +167,16 @@ type WorkspaceTemplates struct { | |
Regular *corev1.Pod `json:"regular"` | ||
} | ||
|
||
type StripePriceIDs struct { | ||
EUR string `json:"eur"` | ||
USD string `json:"usd"` | ||
} | ||
|
||
type StripeConfig struct { | ||
IndividualUsagePriceIDs StripePriceIDs `json:"individualUsagePriceIds"` | ||
TeamUsagePriceIDs StripePriceIDs `json:"teamUsagePriceIds"` | ||
} | ||
|
||
Comment on lines
+170
to
+179
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Hey Milan, I've just joined the team so I'm still catching up on decisions around the installer 😬 How do we decide if things go to "experimental" or not? maybe @mrsimonemms could help clarifying as well? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @ArthurSens as a general rule, anything that's in Things are only added to the main config if it's something that we are happy to publicly support (including community/open source users), we have updated the public documentation (and usually added to the KOTS config) and that we are confident we won't need to amend. Looking at this, it looks like @easyCZ has correctly put it in There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Thanks Simon. Yes, indeed this is config only specific to SaaS at this point, hence defined in the experimental section. |
||
type WebAppConfig struct { | ||
PublicAPI *PublicAPIConfig `json:"publicApi,omitempty"` | ||
Server *ServerConfig `json:"server,omitempty"` | ||
|
@@ -178,6 +188,7 @@ type WebAppConfig struct { | |
Usage *UsageConfig `json:"usage,omitempty"` | ||
ConfigcatKey string `json:"configcatKey"` | ||
WorkspaceClasses []WebAppWorkspaceClass `json:"workspaceClasses"` | ||
Stripe *StripeConfig `json:"stripe,omitempty"` | ||
} | ||
|
||
type WorkspaceDefaults struct { | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see empty strings in the installer config when I ran
kubectl get configmap usage -o yaml
, but I expected these ones for preview?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, it's gonna be because changes to
.werft
don't get triggered by PRs. I need to manually trigger.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've triggered the build. If you look at the preview env now, it does contain the config.
Sorry, this one always catches me out and I forgot to do this for the PR when I created it, I had it on a different branch before.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, looks good!