write-script-ansible

Create a single YAML document with two parts separated by a `---` line: a Windmill header defining extra_vars, inventory, and dependencies, followed by standard Ansible plays. Windmill parses the header to build inputs and runs the plays with ansible-playbook.

Define arguments under `extra_vars` in the script header with a type such as string, number, or boolean. Windmill passes them via `--extra-vars`, making each one available as a Jinja variable like `{{ name }}` inside the plays.

`wmill script preview` executes the local script file without deploying, so it is the default when iterating on edits. `wmill script run` executes the version already deployed in the workspace and should only be used when testing the deployed version.

Editing script content, especially adding imports or changing main's arguments, invalidates the stored content hash and leaves the lock and input schema stale. Run `wmill generate-metadata` to regenerate locks, schemas, and hashes so git-sync and CI stay clean.

Yes. Write JSON to a file named `result.json` in the job directory, for example using the Ansible copy module with content rendered through the `to_json` filter. Windmill reads that file as the script's return value.