API changes

[benlangfeld]

A bunch of work is already underway to separate concerns between Scenario and Runner, and this is almost finished.

A couple of rough proposals:

• [x] Fully separate concerns between Scenario and Runner
  • Runner should take a pre-built Scenario
  • Scenario #compile should be the point at which a path is taken
  • Overhaul CLI - Replace -c and -r options on CLI with full commands, ie sippy_cup run foo_scenario, sippy_cup compile foo_scenario
• [x] Default to using temporary files for generated scenarios unless they are explicitly compiled to disk
• [ ] Allow SippyCup to execute SIPp scenarios using a YAML manifest (replacing steps with embed or similar, passing either filenames or embedded XML scenarios).

Thoughts, @bklang?

[benlangfeld]

See #34 for the start of some of this.

[bklang]

Comments were made in #34. Make sense to close this one?

[benlangfeld]

I'm going to use this as a placeholder for multiple follow-up PRs.

I'd also appreciate feedback on the last point if you have any.

[bklang]

Allow SippyCup to execute SIPp scenarios using a YAML manifest (replacing steps with embed or similar, passing either filenames or embedded XML scenarios).

:+1: This is a great idea.

My ideal preference would be to be able to embed the XML scenario so you can just pass around the single YAML file. But being able to reference an external XML is something we already support.

[benlangfeld]

More coming in #36

[benlangfeld]

Actually, gonna close this in favour of finishing off in #36