feat: document wrapping docket from ansible-dokku - #413
Merged
josegonzalez merged 4 commits intoAug 7, 2026
Merged
Conversation
A new page maps each of the 27 `ansible-dokku` modules onto its docket task across the 73 registered task types, states where the two disagree on which fields are required, specifies the JSON payload a wrapper generates and pipes in, and names what cannot be delegated yet. `apply` gains `--detailed-exitcode`, mirroring `plan`, so a wrapper running one docket invocation per Ansible task reads `changed` off the exit code rather than parsing the event stream; without it `apply` still exits `0` whether or not anything changed. The `validate --json` problem schema was never written down and now sits alongside the apply and plan events, and all three streams ship JSON Schema files under `docs/schemas/`. Closes #409.
This was referenced Aug 6, 2026
Each of the four things a wrapper cannot delegate now points at its tracking issue, so a reader can tell whether the gap is still open without diffing the page against the task registry.
josegonzalez
force-pushed
the
409-document-the-contract-for-wrapping-docket-from-ansible-dokku
branch
from
August 7, 2026 03:22
4f883b9 to
25a2aa2
Compare
|
The `apply --detailed-exitcode` example read `$?` after a pipeline, so it always saw `tee`'s status and never reported a change or a failure. The validate problem table described `block_empty` as an orphan `rescue:`, which is `block_orphan_clause`, and omitted both that code and `envelope_key_unsupported` from the table and from the published schema, so a wrapper validating against the schema would reject a legitimate event. `stdout`, `stderr`, and `exit_code` are now scoped to `apply`, since `plan` emits only `error` and a `check_mode` failure has no `rc` to forward. Masking is scoped too: `--list-tasks` resolves the plan before any sensitive value is registered and does no masking at all, so an interpolated secret comes back verbatim. A new test scans the source for problem code literals and asserts the schema enum matches in both directions, which is what would have caught the two missing codes.
josegonzalez
force-pushed
the
409-document-the-contract-for-wrapping-docket-from-ansible-dokku
branch
from
August 7, 2026 03:23
25a2aa2 to
f49ca2f
Compare
|
josegonzalez
deleted the
409-document-the-contract-for-wrapping-docket-from-ansible-dokku
branch
August 7, 2026 05:53
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A new page maps each of the 27
ansible-dokkumodules onto its docket task across the 73 registered task types, states where the two disagree on which fields are required, specifies the JSON payload a wrapper generates and pipes in, and names what cannot be delegated yet.applygains--detailed-exitcode, mirroringplan, so a wrapper running one docket invocation per Ansible task readschangedoff the exit code rather than parsing the event stream; without itapplystill exits0whether or not anything changed. Thevalidate --jsonproblem schema was never written down and now sits alongside the apply and plan events, and all three streams ship JSON Schema files underdocs/schemas/.Writing the contract down surfaced one pre-existing gap that is documented but not fixed here:
--list-tasks --jsonresolves the plan before any sensitive value is registered and does no masking, so an interpolated secret comes back verbatim inname. Both pages now warn against routing that stream anywhere a secret must not land.The four things a wrapper cannot delegate are tracked in #414, #415, #416, and #417.
Closes #409.