-
Notifications
You must be signed in to change notification settings - Fork 22
0.0.1 Purpose
The initial implementation of GREASE was written in PowerShell as a set of tools for the team to help automate issue creation and resolution.
GREASE is designed to be a general purpose scheduler & automation platform. GRE at Target has thousands of incidents that are ripe for the cold automated hands of the machine. GREASE offers a platform for engineers to configure sets of parameters to trigger actions to take place. This platform also allows for engineers to create actions (called commands) to be executed by the engine. The engine provides this, along with some built in telemetry and logging functionality.
The GREASE platform offers a unified platform for all GRE to implement their automated incident creation/resolution. This is because rather than imposing selection of language or solution type, an engineer can take their pre-existing scripts and programs and simply wrap them in a GREASE command making it available for GREASE to interact with it. When GREASE configuration then finds a situation to execute the new command it will be executed. This hopefully achieving the goal of "write once and forget". This allows GRE to automate the simple stuff and focus on more advanced and technically challenging problems.
GREASE offers a standard configuration language in JSON for telling the engine when to trigger commands to run. A goal of GREASE is to make automating Knowledge Base and other common incidents as easy and transparent as possible. As your command repository grows it won't always be necessary to write a configuration and command to resolve an issue. Thus configuration should be clear and concise to the user and the system to avoid eye crossing insane dependence trees.
