#SoloGeneral - CLI event triggers

1 messages · Page 1 of 1 (latest)

undone trellis
#

Hi there!

#

Taking a look at the fixture for this event

#

Could you share what you see in your terminal window when you run the above command?

safe grail
#
A newer version of the Stripe CLI is available, please update to: v1.11.0
Setting up fixture for: cardholder
Running fixture for: cardholder
Setting up fixture for: card
Running fixture for: card
Setting up fixture for: authorization_request
Running fixture for: authorization_request
Trigger succeeded! Check dashboard for event details.```
#
2022-08-16 15:44:53  <--  [200] POST http://localhost:3000/api/v1/stripe_webhooks [evt_1LXVh2R3aspVTJoeLtAnmybM]
2022-08-16 15:44:53   --> connect issuing_cardholder.updated [evt_1LXVh3R3aspVTJoeB7UfE3cJ]
2022-08-16 15:44:53   --> connect issuing_card.created [evt_1LXVh3R3aspVTJoewajQLBx2]
2022-08-16 15:44:53  <--  [200] POST http://localhost:3000/api/v1/stripe_webhooks [evt_1LXVh3R3aspVTJoeB7UfE3cJ]
2022-08-16 15:44:53  <--  [200] POST http://localhost:3000/api/v1/stripe_webhooks [evt_1LXVh3R3aspVTJoewajQLBx2]
2022-08-16 15:44:55   --> connect issuing_transaction.created [evt_1LXVh5R3aspVTJoeVKKQcQd4]
2022-08-16 15:44:55  <--  [200] POST http://localhost:3000/api/v1/stripe_webhooks [evt_1LXVh5R3aspVTJoeVKKQcQd4]
2022-08-16 15:44:55   --> connect issuing_authorization.created [evt_1LXVh5R3aspVTJoe5ykvjJlc]
2022-08-16 15:44:55  <--  [200] POST http://localhost:3000/api/v1/stripe_webhooks [evt_1LXVh5R3aspVTJoe5ykvjJlc]
2022-08-16 15:44:55   --> connect issuing_authorization.updated [evt_1LXVh5R3aspVTJoefntP1gvs]
2022-08-16 15:44:55  <--  [200] POST http://localhost:3000/api/v1/stripe_webhooks [evt_1LXVh5R3aspVTJoefntP1gvs]
2022-08-16 15:44:56   --> connect balance.available [evt_1LXVh6R3aspVTJoeg45ZzJlX]
2022-08-16 15:44:56  <--  [200] POST http://localhost:3000/api/v1/stripe_webhooks [evt_1LXVh6R3aspVTJoeg45ZzJlX]```
undone trellis
#

This is helpful, thank you!

#

I believe this is a formatting issue with one of the override flags.

#

Do you receive the expected results if you use:
--override authorization_request.held_amount=2150

safe grail
#

Invalid value for override flag (authorization_request.held_amount=2150). The override flag requires the name of the fixture to apply (--override fixtureName:path.to.param=value).

undone trellis
#

which version of the CLI are you on? you can pull this up with stripe version

safe grail
#

stripe version 1.8.11

undone trellis
#

Mind updating? if you use homebrew and the cli was installed using default paths, this should be doable with brew upgrade stripe/stripe-cli/stripe

safe grail
#

After update it still says:

Invalid value for override flag (authorization_request.held_amount=2150). The override flag requires the name of the fixture to apply (--override fixtureName:path.to.param=value).

If I run this:

stripe trigger issuing_authorization.request --stripe-account acct_1L1dQiR3aspVTJoe --override authorization_request:held_amount=2150

it says it is successful but it still does not show up in the event logs anywhere that I can see.

#

Version is now 1.11.0

undone trellis
#

interesting. i do see an issuing_authorization.created event with a 2150 amount. it looks like that was sent to your cli endpoint, too

#

I might not have been super clear. what is the full command you're running when you receive the Invalid value for override flag... error?

safe grail
#

stripe trigger issuing_authorization.request --stripe-account acct_1L1dQiR3aspVTJoe --override authorization_request.held_amount=2150

undone trellis
#

Ah, I think I see what I missed. Could you try:
stripe trigger issuing_authorization.request --stripe-account acct_1L1dQiR3aspVTJoe --override authorization_request:held_amount=2150

safe grail
#

I tried that. The result was the same. Says successful but nothing in the logs

undone trellis
#

Interesting, got it. I was able to trigger the event on my side so I wonder if there's an issue with your local CLI settings after the update. Please don't share the full results of this but try running stripe config --list locally. do you see a value for account_id ?

safe grail
#

yes

amber pivot
#

What is the account id?

safe grail
#

acct_1KhQkEJcIAKVEIOP

amber pivot
#

Thanks! And can you run this again so I can see what populates?

stripe trigger issuing_authorization.request --stripe-account acct_1L1dQiR3aspVTJoe --override authorization_request:held_amount=2150

safe grail
#

I have run it. Let me know if oyu need any of the console output

amber pivot
#

You ran it just now?

safe grail
#

Yes, I ran it as soon as you asked using the command you gave

#
2022-08-16 18:02:19  <--  [200] POST http://localhost:3000/api/v1/stripe_webhooks [evt_1LXXq2R3aspVTJoeiJGZLcfT]
2022-08-16 18:02:19   --> connect issuing_card.created [evt_1LXXq3R3aspVTJoecVQgiXFQ]
2022-08-16 18:02:19   --> connect issuing_cardholder.updated [evt_1LXXq3R3aspVTJoeoa1pswtH]
2022-08-16 18:02:19  <--  [200] POST http://localhost:3000/api/v1/stripe_webhooks [evt_1LXXq3R3aspVTJoecVQgiXFQ]
2022-08-16 18:02:19  <--  [200] POST http://localhost:3000/api/v1/stripe_webhooks [evt_1LXXq3R3aspVTJoeoa1pswtH]
2022-08-16 18:02:21   --> connect issuing_transaction.created [evt_1LXXq5R3aspVTJoe6AwCla3n]
2022-08-16 18:02:21  <--  [200] POST http://localhost:3000/api/v1/stripe_webhooks [evt_1LXXq5R3aspVTJoe6AwCla3n]
2022-08-16 18:02:21   --> connect issuing_authorization.created [evt_1LXXq5R3aspVTJoebNmy1e86]
2022-08-16 18:02:21  <--  [200] POST http://localhost:3000/api/v1/stripe_webhooks [evt_1LXXq5R3aspVTJoebNmy1e86]
2022-08-16 18:02:21   --> connect issuing_authorization.updated [evt_1LXXq5R3aspVTJoelKoAKpC6]
2022-08-16 18:02:21  <--  [200] POST http://localhost:3000/api/v1/stripe_webhooks [evt_1LXXq5R3aspVTJoelKoAKpC6]
2022-08-16 18:02:22   --> connect balance.available [evt_1LXXq6R3aspVTJoeTqntlNH3]
2022-08-16 18:02:22  <--  [200] POST http://localhost:3000/api/v1/stripe_webhooks [evt_1LXXq6R3aspVTJoeTqntlNH3]```
amber pivot
#

That seems to be working just fine. The event fires and the amount is updated:

safe grail
#

My apologies. i must have been looking at the wrong event log. Thank you for the clarification