Separate local preparation from deployment prerequisites
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# Feature 0016: Deploy the D&D Pipeline to `pipeline-dnd`
|
||||
|
||||
Status: blocked
|
||||
Status: ready
|
||||
|
||||
## Summary
|
||||
|
||||
@@ -193,8 +193,11 @@ immediate identical Ansible run reports no changes.
|
||||
|
||||
## Operational Prerequisites
|
||||
|
||||
Before implementation, establish the concrete deployment context and record
|
||||
the non-secret choices in the implementation plan or deployment runbook:
|
||||
Local repository preparation and syntax/dependency checks can proceed with the
|
||||
workspace's existing Ansible virtual environment. Before live deployment,
|
||||
establish the controller, target access, and Vault details below. Select the
|
||||
session/audio before the end-to-end exercise, not before local implementation.
|
||||
Record non-secret choices in the implementation plan or deployment runbook:
|
||||
|
||||
- Identify the operational Ansible controller and its deployment checkout.
|
||||
The repository configuration currently selects `/etc/ansible/inventory`,
|
||||
|
||||
Reference in New Issue
Block a user