Skip to content

Instantly share code, notes, and snippets.

@dbarrosop

dbarrosop/Brigade_naming.rst Secret

Created December 28, 2016 10:15
Show Gist options
  • Save dbarrosop/33a2b68b1afa337c1ef9b1588a3fced0 to your computer and use it in GitHub Desktop.
Save dbarrosop/33a2b68b1afa337c1ef9b1588a3fced0 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
Brigade_naming.rst

Regarding naming. I know some people wanted to talk about that. I was thinking the following names

  • tactic. A module that provides some functionality
  • planning phase. The pre section.
  • execution phase. The tasks section.
  • analysis phase. The post section.
  • plan. The runbook/playbook, the yaml describing what to do.

And our motto: "I love it when a plan comes together" (@GGabriele is probably too young to get this one ;) )

So a plan consists of a set of tactics divided in the planning, execution and analysis phases. We could also add aliases like cleaning (alias for analysis) or intel (alias for planning) so people can categorize their tasks more accordingly. @jedelman8 mentioned something along these lines but I am not sure it's useful other than "it looks good xD"

Thoughts?

@ogenstad
Copy link

The name analysis implies verification of what happened. This step could also be to things like log the job or close a change in a system like ServiceNow or something. Something like paperwork might be broader. recon -> execution -> paperwork, but it's also nice if it's fairly clear what the things mean so you don't have to read a manual just to understand. Perhaps analysis is better.

tactic sounds wrong for a module though. Something like operation would be better.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment