#jairo094215_api
dim inletBOT
👋 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/1428697800123875411
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
wide elm
👋
Data in Sandboxes are isolated and can't be migrated copy paster from one to another
You need to redefine your integration design accordignly
You can't have same Id in multiple sandboxes
You can create a script that creates your test data in your sandbox for example.
limpid fulcrum
We built a script for this, but at that point we realized it wasn't respecting the IDs. Does this mean it's impossible to maintain the same IDs?
But our application is based on Stripe subscriptions, and therefore all products are created there. In our application, it's necessary to know the corresponding Stripe ID for each product at all times. How else could we operate without having to know the product IDs on our end?
wide elm
We built a script for this, but at that point we realized it wasn't respecting the IDs. Does this mean it's impossible to maintain the same IDs?
Yes you can't maintain the same IDS.
But our application is based on Stripe subscriptions, and therefore all products are created there. In our application, it's necessary to know the corresponding Stripe ID for each product at all times. How else could we operate without having to know the product IDs on our end?
Wait, the goal of using Sandboxes is to test, what is your use case here ?
How else could we operate without having to know the product IDs on our end?
You can list the available products using Stripe API on each Sandbox
Not sure I understand the blocker here, sorry
limpid fulcrum
Well, our use case is that until now all development teams work using the same testing environment (the one for the main account). With the arrival of the new Sandbox environments, we thought we could provide an independent Sandbox to each team without having the risk of someone breaking something in the main test environment (configurations, webhooks, deleting products, etc.). The limitation is that if the product IDs are not respected, then our application will not work.
wide elm
If you want to have a Sandbox for each team, you need to provide them a different env of your application too. You shouldn't have multiple Sandboxes with one single app... you should for each Sandbox have an app env on your side
and each env maps the corresponding sandbox
limpid fulcrum
Yes, from the beginning with the term Sandbox I was referring to the test environments that can be created recently.
we need some test environments, all with the same prices/products/plans with same IDs
wide elm
No you can't have the same IDS in all environment, you need to remove this dependency in your design
of your testing envs
Can you share a concrete issue you are facing when having different IDs from one sandbox to another
limpid fulcrum
Yes, of course. On our SAAS platform, features/add-ons are based on a subscription payment model supported by Stripe. In the feature catalog, customers can select the desired items and subscribe to them. This feature/add-on catalog is static, and in JSON files we have the mapping of all products to their corresponding Stripe IDs. Therefore, when we call the subscription API, we use those IDs to indicate the subscription items.
If we point the application to a test environment where there are no products with the IDs listed in the JSON files of our application, then the subscription system becomes inoperative.