fix: resolve Galaxy validation errors in argument_specs

[sbaerlocher]

Summary

Fixes Galaxy validation errors in K3s and Fleet roles that prevented proper indexing on Ansible Galaxy.

K3s Role - 3 Validation Errors Fixed

Issue:

entry_points -> agent -> options -> k3s_token -> no_log
  Extra inputs are not permitted (type=extra_forbidden)
entry_points -> main -> options -> k3s_token -> no_log
  Extra inputs are not permitted (type=extra_forbidden)
entry_points -> server_join -> options -> k3s_token -> no_log
  Extra inputs are not permitted (type=extra_forbidden)

Fix:

• Removed invalid no_log field from argument_specs.yml
• The no_log parameter is not supported in the argument_specs schema
• Sensitive data protection is handled in tasks using no_log: true on task level, not in specs

Fleet Role - 10 Validation Errors Fixed

Issue:

entry_points -> bundles -> options -> fleet_bundles -> description
  Field required (type=missing)
entry_points -> bundles -> options -> fleet_bundles -> fleet_bundles
  Extra inputs are not permitted (type=extra_forbidden)

(And similar errors for clusters, gitrepos, workspaces, registration_tokens)

Fix:

• Replaced YAML anchor references (<<: *anchor) with explicit descriptions in entry_points
• Galaxy validation requires top-level description fields
• Maintained type, elements, and default values for all fleet_* variables

Impact

These changes allow both roles to be:

• Properly validated by Ansible Galaxy
• Correctly indexed and searchable
• Fully documented in the Galaxy UI

Test Plan

• Removed invalid no_log fields from k3s argument_specs
• Replaced YAML anchors with explicit descriptions in fleet argument_specs
• Verify Galaxy validation passes on next publish
• Verify role documentation appears correctly on Galaxy

🤖 Generated with Claude Code