Skip to content

docs: explain that a dynamic target may name a group or tag - #374

Merged
umputun merged 1 commit into
masterfrom
docs-dynamic-target-groups
Nov 1, 2026
Merged

umputun merged 1 commit into
masterfrom
docs-dynamic-target-groups

Conversation

@umputun

@umputun umputun commented Nov 1, 2026

Copy link
Copy Markdown
Owner

the dynamic targets section didn't say what the variable may hold. It is resolved like any other targets entry, so a playbook target, inventory group or tag expands to all its hosts, while a list of hosts in the variable is treated as one host address. Added a short paragraph with an example to README, and synced the site copy.

Related to #307

Copilot AI balanced review requested due to automatic review settings November 1, 2026 17:26

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

No active review issues are reported for this documentation-only clarification of dynamic target resolution.

No open issues 🎉

What changed in this PR

Clarifies how Spot resolves dynamic target variables, with matching documentation in the README and site source. No runtime behavior changes.

Changes:

  • Explains that a variable can name a playbook target, inventory group, or tag and expand to all its hosts.
  • Adds a group-targeting example and clarifies that space-separated host lists are treated as one host address.
File Description
site/​docs-src/​index.md Mirrors the dynamic target clarification in the site documentation.
README.md Documents target expansion, a group example, and host-list limitations.

Review effort: Balanced

@umputun
umputun merged commit 076426a into master Nov 1, 2026
5 checks passed
@umputun
umputun deleted the docs-dynamic-target-groups branch November 1, 2026 17:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants