#zachm_api
1 messages ยท Page 1 of 1 (latest)
๐ 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/1435859120505884713
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hey! do give me some time to take a look at this
Could i clarify if you receive an error when you try to run a live mode command?
No errors, just have to auth every time. And when I go to auth, it only lets me select testing or sandbox mode.
I want to be able to run live mode commands to read in my shell.
Could you send me an example CLI command that you ran and was asked to authenticate
Do remember to remove any apiKeys or mask it (e.g. sk_test_xxx)
Absolutely anything with --live flag. For example, stripe subscriptions list --live
You would have to specify this flag as well --api-key with the live mode or test mode secret key
What's the point of the --live flag then?
I don't want to have to be pasting a live api key into my terminal constantly, that is a major security concern.
Where did you see the --live flag from?
I dont think we have such a flag: https://docs.stripe.com/cli/flags#flags-Flags
You dont have to keep pasting it
Directly from the stripe docs
For example, https://docs.stripe.com/cli/listen#listen-live
How else would I specificy the api key using --api-key?
This is for the stripe listen webhook command, it is specific to stripe listen command, and only can come after the listen
yup, give me a while to come up with an example!
You mentioned here that I needed the --live flag as well as the --api-key flag, so again, what's the point of the --live flag? Why are there config vars for api keys?
I mentioned a lot more than just the listen command. --live is a valid flag for any stripe CLI command.
Hello?
hey! Yes upon checking the documentation and testing it out, --live flag, it is meant to make live requests
Was there a prompt to allow your terminal to access live mode api keys?
If you checked "Always allow", the prompt to re-authenticate would have stopped appearing
So, was I correct or not?
No, as I said: the option to authenticate with the live environment isn't even there
See this message
I can only select testing or sandbox when authenticating
Could you share with me a screenshot of this?
Did you ever get this example?
Man, can you just trust me that this is happening and help find a solution? I feel like I'm just arguing about whether flags are valid or not and whether this is actually happening or not
Or is there anyone else that has more knowledge around the stripe CLI that can help out here? @hearty jungle
Hmmm, that is weird, could i get your account ID to investigate this further? (acct_xxx) I will also be roping my colleague in on this
@hearty jungle
@hearty jungle
acct_1PQMtGKYO7HzkIIT
@hearty jungle you still there?
Yup, do give me some time, we are testing it out again on our end again
All good, just hoping to get responses to my questions above.
Hey we just tested this out and realised that the โ-live flag only works when the CLI is authenticated with test mode, and will not work when it is authenticated with Sandbox mode.
Could you test this out on your end as well?
Yeah we only use test mode
We never use sandbox
Hey! Taking over for my colleague. Let me catch up.
Could you please clarify why you want to make live request with the stripe cli ?
Stripe CLI is just for tests and it's not reliable for live and production integration. You should be using Stripe SDKs in your production/live integration