liveBook · Manning

Automation goal

As explained in Practical Automation with PowerShell: Effective scripting from the console to the cloud

An intended outcome or set of outcomes that an automation process is designed to achieve.

An automation goal states what a specific automation must achieve. Define it broadly enough to include operational constraints, not just the most visible problem; the goal guides the actions and can become a design checklist. section 1.2 section 1.2.1

Preserving web-server logs

A log-cleanup automation aims to prevent drives from filling while retaining audit-required data and keeping it accessible when needed. Compressing and moving old logs fits infrequent access; moving them to larger storage better fits regular access. section 1.2 section 1.2.1

Use the goal to shape the automation design:

  • Identify the primary outcome and every constraint that must remain satisfied. section 1.2.1
  • Turn the stated outcomes into a checklist for designing automation actions. section 1.2.1
  • Reconsider actions when access, retention, or other requirements change. section 1.2.1

How Practical Automation with PowerShell: Effective scripting from the console to the cloud covers it

How deep it goes
Defines goals and works through how added data-retention and access requirements alter planned actions.
Examples
Uses web-server logs that must be retained for security audits while preventing drive exhaustion.
What you can do after
Evaluate/understand automation requirements and select actions that satisfy both primary outcomes and operational constraints.
How it connects
Connects automation goals with triggers, actions, maintainability, long-term storage, and security audits.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Practical Automation with PowerShell: Effective scripting from the console to the cloud. The section links point to the parts of the book it draws on.