#nukes-cli-installation
1 messages · Page 1 of 1 (latest)
@pearl wedge I don't know much about installation systems so you might be better off filing a detailed report on https://github.com/stripe/stripe-cli/issues if it's really specific.
I'm happy to chat about it and flag internally if I can help though.
I'm really curious what kind of workflow you're using that makes you install the CLI repeatedly at certain times of the day where it's been frustrating enough to realize this is happening
nukes-cli-installation
$ echo -e "[Stripe]\nname=stripe\nbaseurl=https://packages.stripe.dev/stripe-cli-rpm-local/\nenabled=1\ngpgcheck=0" >> /etc/yum.repos.d/stripe.repo
$ yum install --assumeyes stripe
Loaded plugins: ovl
Resolving Dependencies
--> Running transaction check
---> Package stripe.x86_64 0:1.14.6-1 will be installed
--> Finished Dependency Resolution
Dependencies Resolved
================================================================================
Package Arch Version Repository Size
================================================================================
Installing:
stripe x86_64 1.14.6-1 Stripe 6.9 M
Transaction Summary
================================================================================
Install 1 Package
Total download size: 6.9 M
Installed size: 19 M
Downloading packages:
https://packages.stripe.dev/stripe-cli-rpm-local/stripe/1.14.6/x86_64/stripe.rpm: [Errno 14] HTTPS Error 403 - Forbidden
Trying other mirror.
Error downloading packages:
stripe-1.14.6-1.x86_64: [Errno 256] No more mirrors to try.
this is a CI/CD job that runs overnight to update dependencies every weekday between midnight and 5am pacific
I use the stripe CLI in automated integration testing to trigger test events.
Gotcha. I would highly recommend mocking our API entirely and not relying on real behaviour like this in real tests personally
And for that report, I think a detailed report on a Github issue with all that information and context will be the best next step
I do have mocked tests as well, but I always throw in at least one test that runs in our nonprod environment using the Stripe test mode to ensure that everything is still integrated correctly.
I've been burned before only using mocked integrations to find out it doesn't work as mocked in some cases.
yeah that's fair
I'll file the github issue, thanks!
let me know once you have and I'll flag to the eng team internally to have a look, that 403 is really strange