caravel graph

The deployment's resources and what each depends on, as Graphviz DOT (caravel graph | dot -Tsvg > lane.svg), or as JSON. Dashed edges restart their target when their source changes

The deployment's resources and what each depends on, as Graphviz DOT (`caravel graph | dot -Tsvg > lane.svg`), or as JSON. Dashed edges restart their target when their source changes

Usage: caravel graph [OPTIONS] [LANE]

Arguments:
  [LANE]  The lane file (the same as -f)

Options:
  -f, --file <LANE_FILE>   The lane file, or a directory with a lane.toml (also CARAVEL_FILE)
  -e, --env <NAME>         The deployment, [env.<name>] (also CARAVEL_ENV)
      --json               Print JSON on stdout, for scripts; progress and notes go to stderr
      --release-dir <DIR>  A release to install (also CARAVEL_RELEASE_DIR); default: the one installed with caravel, else this checkout's builds
      --wasm-dir <DIR>     Take the contracts from here instead, e.g. the CI contracts-wasm artifact (also CARAVEL_WASM_DIR)
      --var <NAME=VALUE>   Set one of the lane file's vars; repeat for more. Read by the var's type (lists and maps as TOML: --var 'validators=["1","2"]'). Also CARAVEL_VAR_<name>
      --var-file <FILE>    A TOML file of var values (name = value); later files win, and --var over them
  -h, --help               Print help