Skip to content

Initial commit: itential.valkey collection - #1

Closed
Amunagala-itential wants to merge 1 commit into
mainfrom
add-valkey-collection
Closed

Amunagala-itential wants to merge 1 commit into
mainfrom
add-valkey-collection

Conversation

@Amunagala-itential

Copy link
Copy Markdown
Collaborator

Summary

Initial scaffold of the standalone itential.valkey Ansible collection: installs Valkey as a Remi-free, EL9/Amazon Linux 2023-only alternative to itential.deployer's redis role.

This collection is transitional — it exists separately from itential.deployer only until roles/redis is retired there, at which point roles/valkey and its playbooks are intended to be merged directly into itential.deployer.

Depends on itential.deployer at runtime for the shared common/offline utility roles (referenced by FQCN).

Contents

  • roles/valkey/ — the role, ported from itential.deployer's in-progress PR (#374 there), with common/offline calls rewritten to FQCN and internal variables renamed with a valkey_ prefix for namespace safety
  • playbooks/valkey.yml, verify_valkey.yml, certify_valkey.yml, download_packages_valkey.yml
  • docs/valkey_guide.md, example_inventories/valkey/
  • CI scaffolding matching itential.deployer's conventions (ansible-lint, role-readme-check, changelog/publish workflows)

Test plan

  • ansible-lint clean (0 failures) with both itential.valkey and itential.deployer registered as collections
  • Live-tested against real AWS-hosted Rocky 9 hosts across HA2 (colocated Sentinel) and ASA (dedicated Sentinel) topologies: certify_valkey.yml passes clean on all hosts, cross-collection FQCN resolution confirmed working end-to-end

Standalone Ansible collection installing Valkey as a Remi-free,
EL9/Amazon Linux 2023-only alternative to itential.deployer's redis
role. Depends on itential.deployer at runtime for the shared common
and offline utility roles.

This collection is transitional: it exists separately from
itential.deployer only until roles/redis is retired there, at which
point roles/valkey and its playbooks are intended to be merged
directly into itential.deployer.
@Amunagala-itential

Copy link
Copy Markdown
Collaborator Author

Superseded — restructuring to use dev as the default branch, per the fork-based workflow used for itential.deployer. Content now lives on dev directly.

@Amunagala-itential
Amunagala-itential deleted the add-valkey-collection branch September 16, 2026 15:48
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.

1 participant