All right my friends here's the moment of truth.
We are going to manually create a ticket well then manually create an order for that ticket and then
hopefully we're going to see that console log.
We had put together inside of our key right here.
We should see something immediately that says I want to publish while the while all that stuff.
Let's open up postmen and get to it.
I've got post band right here as usual going to want to make sure that we are signed in.
It looks like I currently am signed in.
That's our get request to API users current user.
Make sure you are signed in as a person all then create a brand new ticket so this can be opposed to
API slash tickets with the title and a price looking to send that off.
It looks good.
I'm going to take that I.D. And I'm going to create an order with this ticket I.D. so to create an order
we will make a post request to HDD P.S. oh and slash slash ticketing dot Dev API orders.
I'll go to headers but in a content type of application slash Jason I'm going to go over to body select
raw and the only thing that we need to create a new order is the ticket I.D..
So I'm going to enter a Jason object right here with ticket I.D. and then paste in the idea that ticket
that I just created remember this is Jason that we're entering.
So make sure you get those double quotes right there.
Also make sure that you've got a lowercase d on I.D. We'll also make sure that we've got Jason selected
over here and that should be at they'll then go ahead and send this off I should immediately see that
I have created a brand new order.
Yep looks good.
Then I'll go back over my terminal and we'll see how we are doing.
OK.
So over here.
Well lot of events going on here.
So I see in some order I see the ticket created.
That's the reception I see a publisher of ticket created and then inside a kind of a strange order here.
Nonetheless remember all these counts logs kind of get jumbled up because of how scaffold handles them.
So it's kind of hard to read but we can kind of see that everything more or less worked as expected.
So I've got an event published of order created.
It looks like tickets received order created and expiration received order created as well.
Expiration once it received that order created event and then created a new job and published it over
to read.
Because we did not put any delay on receiving or processing that event.
We then immediately received that job back and we did a I want to publish an expiration complete event
for order I.D. blah blah blah okay.
So I'd say that that looks pretty good it means that we are successfully receiving the order a created
event.
We then successfully create the job and then we successfully received that job right then immediately
in the future.
The next obvious thing that we need to add inside of here is to make sure that we delay receiving this
event or somehow put in that 15 minute delay that we do not immediately get it back this job back to
process.
We want to make sure we've got that 15 minute delay inside of here.
Let's take a look at how we're going to add in that 50 minute delay.
Pretty easy straightforward.
We'll take care of that in just a moment.