Skip to content

refactor: rename preflight role to validate_environment - #110

Open
vvaldez wants to merge 2 commits into
redhat-cop:v2from
vvaldez:rename-preflight
Open

vvaldez wants to merge 2 commits into
redhat-cop:v2from
vvaldez:rename-preflight

Conversation

@vvaldez

@vvaldez vvaldez commented Oct 23, 2026

Copy link
Copy Markdown

Summary

Renames the preflight role to validate_environment, pairing with validate_migration (companion PR #108, post-migration validation). Plain descriptive names replace the aviation metaphor; the pair stays symmetric.

Compatibility

Clean break: v2 is unreleased and nothing in-repo consumed the old names. Renamed surfaces:

  • Role dir roles/preflight → roles/validate_environment
  • Playbook vmf_preflight.yml → vmf_validate_environment.yml
  • User variables preflight_* → validate_environment_* (including internal __preflight_* facts)
  • Test target preflight_report → validate_environment_report
  • GLOSSARY.md (new), architecture diagram node, changelog fragment (rewritten to final-state naming per the unreleased-changelog consolidation)

NOTE: preflight is days old (merged via #107, unreleased), so no external consumers are known. If you have automation referencing the old names, update it when pulling v2.

Validation

  • ansible-lint production profile (strict), full pre-commit
  • Integration target regression run: identical recap pre/post rename
  • Documentation regenerated with the CI-pinned docsible version

Attribution: created using opencode (session: ses_ed904e798ffeTYJVsSCQP9sbvM)

@vvaldez vvaldez self-assigned this Oct 23, 2026
@vvaldez
vvaldez deployed to external-ci October 23, 2026 15:37 — with GitHub Actions Active
Pair symmetry with validate_migration (companion PR redhat-cop#108, post-only).
Clean break: v2 is unreleased and nothing in-repo consumed the old
names. Role dirs, playbooks (vmf_validate_environment.yml), variable
prefixes, test targets, docs, and the changelog fragment all use the
new name.

Assisted-by: opencode:enmaas/rits/zai-org/glm-5-3
@vvaldez
vvaldez deployed to external-ci October 23, 2026 15:59 — with GitHub Actions Active
@vvaldez
vvaldez marked this pull request as ready for review October 23, 2026 16:54
@vvaldez
vvaldez requested a review from sabre1041 as a code owner October 23, 2026 16:54
tech2734
tech2734 previously approved these changes Oct 23, 2026

@tech2734 tech2734 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.

Looks good — clean mechanical rename with no leftover preflight references in the new code. Variable naming, file structure, changelog, architecture diagram, and test target are all consistent. The new GLOSSARY.md is a nice touch for domain vocabulary.

One minor observation (non-blocking): validate_environment_* is verbose (e.g. validate_environment_aap_validate_certs), but the symmetry with validate_migration_* justifies it.

Tested the original preflight role against the homelab in PR #107 review — the logic here is identical, just renamed.

Drop the task-level tags (always/openshift/validate/cnv/mtv/aap/
vcenter/vddk) from validate_environment — no other role in the
collection uses task tags, and all checks already run on every
invocation regardless. Add the empty galaxy_tags key to meta/main.yml
to match the existing roles' metadata shape.

Assisted-by: opencode:enmaas/rits/zai-org/glm-5-3

@sabre1041 sabre1041 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@vvaldez Moving in to the right direction. However, I do not see the conditional that will limit what type of checks are performed (move from tag to property based conditionals)

This branch was successfully deployed

1 active deployment
external-ci — 9f7d6685 Deployed Oct 24, 2026 by vvaldez via external-approval #763
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.

3 participants