Fugue Cheat Sheet¶
Fugue only requires a few things to get started:
- Visit the Download Portal to get the Fugue Client Tools
- Configure your AWS credentials
- Initialize a project with
fugue init <region>or with environment variables
- Issue a
Some high level basics for compositions:
- Compositions are also known as Ludwig files and are denoted by the
compositionkeyword. Read a bit about how they work.
- Only a composition can be run by the
- Imports allow you to import specific modules from the Fugue Standard
import Fugue.AWS.EC2 as EC2.
- Compositions include bindings, which are like variables that follow
the form of
The following commands can easily get you started:
fugue run <composition.lw>- Launch a process
fugue update <alias/FID> <composition.lw>- Update the process
fugue status- Check the status of a process or processes
fugue kill <alias/FID>- Kill the process
Check out the CLI Reference to see all of the available commands.
Verify Before You Deploy¶
These functions enable you to evaluate configurations before they’re implemented:
- Use the
--dry-runflag to see a preview of how AWS will provision your infrastructure with
- Check out Design-Time
lwc <composition.lw>(with an imported validation module), or
lwc <composition.lw> --validation-modules <validation.lw>(without an imported validation module).
fugue policy command and subcommands allow you to manage
role-based access control policy
fugue policy generate-secret- Generate a new secret for a specific user
fugue policy rbac-attach- Attach a policy to the Conductor
fugue policy rbac-detach- Remove the policy from the Conductor
fugue policy list-users- Display a list of all users
To learn more about validations, check out an example.