#john_entitlements-feature

1 messages · Page 1 of 1 (latest)

median sealBOT
dry sandBOT
#

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

median sealBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1240702110903959625

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

atomic snow
#

john_entitlements-feature

#

This is all API only right now!

#

I wouldn't use the CLI personally and I would write code that can control all my products, their features and entitlements. But it doens't have to be part of your whole application's lifecycle you're right. It can be some admin tool/migration script you use when you set things up

#

you will likely need to create new ones over time for example

sage geode
#

Ah okay, is the reason you wouldn't recommend using the CLI that there's no record of the products, features, and entitlements afterwards?

atomic snow
#

No, just a preference. The CLI is not as easily scriptable/repeatable and I much prefer writing real reusable code.

#

I see the CLI more as a debugging tool personally

sage geode
#

Oh I see. I don't have much experience working external scripts into a migration system, especially with our CI/CD pipeline (GitHub actions). Do you have any tips on the best approach here?

#

I can write a Python script to setup the features and entitlements once, for example, but I'm not sure where to go from there.

atomic snow
#

What will you do in a few months when you want to change your features? Will you delete it all and restart fresh? That's kinda how I'm thinking about this, plan for the future and having a script that can take some input (JSON, YAML, etc.) that will create/reflect the right products in your account.
This wouldn't really be part of your CI/CD pipeline

sage geode
#

So a script that takes the API key and a JSON or YAML file as arguments, creates/updates products, and can be run anytime on a dev PC would do the trick?

atomic snow
#

for example yes. And over time you will likely build some automation in your systems for example after a deploy you check if the data in your own JSON matches what's in the API. But to start, a one-off script is the easiest I'd say

sage geode
#

Awesome, thank you! Only issue is the marketing team frequently uses the dashboard to change products and pricing. Will have to get them to go through the script instead.

atomic snow
#

👍