Very interesting. I‘m not very knowledgeable in the payment space, unfortunately. Do you think there is a way to abstract the concepts over multiple, pluggable payment providers (other than Stripe) in the future?
Show HN: Tier.run – Terraform for Stripe
21–30 of 49 posts
Re: Show HN: Tier.run – Terraform for Stripe
#22We don't have SaaS apps but having something like that for in-app purchases that will deploy over App Store, Google Play and PayPal at once would be appreciated. Just a suggestion.
Re: Show HN: Tier.run – Terraform for Stripe
#23How is this better than the Stripe Terraform provider? https://registry.terraform.io/providers/franckverrot/stripe/...
Re: Show HN: Tier.run – Terraform for Stripe
#24From the Pricing JSON page, on the 'Why Each Plan Must Have At Least One Feature' question, it says: > Without this restriction, it would be significantly more expensive to fetch your pricing model from Stripe's data. I didn't quite get that. I understood that application code should reference features (and not plans directly) so it becomes easier to change plan structure (via https://priceops.org/4-entitlement ), bu…
It's a fairly common occurrence (I think) that when you are running a query against some store and there is nothing to filter by, you get all the results back. Now the client has to sift through the result set and find products with an empty feature list on the receiving end.
The fix is to add a "no features" placeholder feature and look for it when you are trying to find plans without any features.
Re: Show HN: Tier.run – Terraform for Stripe
#25I'm not in that problem domain in order to know: why make "like terraform, but for stripe" when you could have made "terraform-provider-stripe" and then been _actual_ terraform for stripe? Because the recipes still look like they're targeting a very technical user, which was my mental model for why one would build a whole new DSL
Because controlling the stack allows you to monetize it later.
Re: Show HN: Tier.run – Terraform for Stripe
#26Earlier quoted context omitted.
Perhaps I will regret using that tagline. It's an analogy covers half the functionality. Tier does set up and manage your stripe account based on your pricing.json config, but we go further than that with metering, feature flag style entitlement checks, and other things we plan to provide that you couldn't do as just a provider.
There are terraform providers for DNS services, Database configuration, CI services and all sorts of other things. It's actually not that hard to write a something that wraps configuration state of various APIs into a terraform module. Now, I don't really know the Stripe API besides a quick skim a few years ago, but I think that it's a fully reasonable comment and expectation that when someone says "Terraform for ran…
And combine it with cdktf you can use actual code, shared consts, and have a reliable setup in a common language rather than a JSON DSL.
Re: Show HN: Tier.run – Terraform for Stripe
#27I'm not in that problem domain in order to know: why make "like terraform, but for stripe" when you could have made "terraform-provider-stripe" and then been _actual_ terraform for stripe? Because the recipes still look like they're targeting a very technical user, which was my mental model for why one would build a whole new DSL
Isn't stripe "like terraform, but for online payment methods" ?
But I guess everything is a provider depending on how you look at it.
Re: Show HN: Tier.run – Terraform for Stripe
#28not sure why this needs to be a product... stripe already facilitates price versioning. shouldn't be too hard to sync with my app. my app is tiny right now so I'm doing it by hand but building a little sync command wouldn't take me more than a day.
That’s exactly why this is needed
Re: Show HN: Tier.run – Terraform for Stripe
#29Earlier quoted context omitted.
There are terraform providers for DNS services, Database configuration, CI services and all sorts of other things. It's actually not that hard to write a something that wraps configuration state of various APIs into a terraform module. Now, I don't really know the Stripe API besides a quick skim a few years ago, but I think that it's a fully reasonable comment and expectation that when someone says "Terraform for ran…
And combine it with cdktf you can use actual code, shared consts, and have a reliable setup in a common language rather than a JSON DSL.
Use HCL and you can use actual code, shared consts, and have a reliable setup in a fit-for-purpose (declarative) language rather than a JSON DSL.
Re: Show HN: Tier.run – Terraform for Stripe
#30We don't have SaaS apps but having something like that for in-app purchases that will deploy over App Store, Google Play and PayPal at once would be appreciated. Just a suggestion.
I love that idea. I'm not very experienced with the mobile app stores, but will take a closer look. We've had requests for AWS marketplace as well, which is different from the mobile app stores but the concept would be the same.