Close out the D&D deployment playbook feature
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# Feature 0016: Prepare the D&D Deployment Playbook for `pipeline-dnd`
|
||||
|
||||
Status: in_progress
|
||||
Status: done
|
||||
|
||||
## Summary
|
||||
|
||||
@@ -75,8 +75,9 @@ completion. Future operator-supplied values should be Vault-encrypted in Git;
|
||||
the suite's existing restricted runtime secrets files remain the delivery path.
|
||||
|
||||
The manifest pins the collection to
|
||||
`46913446765e86ecfb29ebad9955d579ef6a4c7e`, containing reviewed pipeline commit
|
||||
`51566afcf69083cdbb5b5718f2544c86b079001c`. Its five standalone role dependencies
|
||||
`2a53979069ff8d091172650729ae2135c1603163`, containing pipeline commit
|
||||
`f48008aa38e1c50adde18aa455d12a8ad77023c2` with Narratio v2.1.2.
|
||||
Its five standalone role dependencies
|
||||
use their reviewed `v0.1.0` tags, with `ansible.posix` `2.2.0` and
|
||||
`community.general` `13.3.0`. Suite Git dependencies use public Gitea URLs;
|
||||
native collections come from Galaxy. Local sibling checkouts are not dependencies.
|
||||
@@ -135,9 +136,12 @@ Ansible task, runtime test harness, or deployment automation is needed.
|
||||
## Dependencies and Follow-up Work
|
||||
|
||||
Features 0013–0015 supply public dependencies, operator enrollment, and storage
|
||||
policy. Feature 0016's consumer preparation already exists in `12b2462`, with
|
||||
initial documentation in `716a80e`; remaining work aligns comments and docs
|
||||
with the user's clarified scope.
|
||||
policy. Consumer preparation was completed in `716a80e`, `12b2462`, and
|
||||
`7f8353d`, and passed independent review with no remediation findings.
|
||||
Public dependency installation, target-only host listing, syntax checking,
|
||||
and whitespace validation passed. Subsequent consumer commit `7f4c90a`
|
||||
updates the collection pin for the Narratio v2.1.2 bug fix; collection build
|
||||
and syntax validation passed. These changes are committed and published.
|
||||
|
||||
The operator may later provision Vault values, install dependencies on their
|
||||
controller, deploy to the host, and validate real processing/publication.
|
||||
|
||||
Reference in New Issue
Block a user