The the automation document language seem very comparable to ansible ,only instead of tasks you have actions, but do you get the same visibility? I would imagine it would be easy to query an automation doc execution for each specific step and know it's error ,but if a single task has failed , would you know by way of api which one that is?
I'm sorry to hear that you're having trouble with this. Our re:Post community may be able to assist. Be sure to post more info about the issue you're facing, here: go.aws/3zG7KhN. ^CM
19:01 "you can do this in the web ui but i'm a fan of the command line" what a convenient way to not show the script building process in the web ui because it simply doesn't exist there...
Hate the fluff in talks like this. I'm sure Darko thought he was being clever and engaging with stories of steam engines and pulleys and levers, but really it's just distracting and undermines the presentation. Every time he goes into one of these clever tangents I just want to hit the skip forward button...but I can't...because I'll jump over actual information. So I'm just basically trapped, no longer thinking of the subject, just stewing in annoyance waiting on this guy to get to the point. "So we invented this nifty thing called 'code'!". Seriously folks, read the room, does the presenter really think anyone watching a re:Invent Systems Manager talk needs an explanation of what code is or why we use it? I wonder if the assignment was a 30 minute presentation and the fluff added to bulk it out since there's really only 10 minutes of useful information presented here.
