Skip to content

Delete pre-rename node refusal and legacy generation handling - #274

Merged
SaladDay merged 1 commit into
mainfrom
codex/installer-legacy-node
Sep 30, 2026
Merged

SaladDay merged 1 commit into
mainfrom
codex/installer-legacy-node

Conversation

@SaladDay

@SaladDay SaladDay commented Sep 30, 2026 •

Copy link
Copy Markdown
Collaborator

Why

The project is not public, so it keeps no backward compatibility. Pre-rename detectors, hints and conversion code are deleted. Another session is cleaning the rest of the repository; this PR covers the node installer. Installer and oac legacy code follows in a later PR, after the in-flight installer PRs merge.

What

  • node_install.py loses the pre-rename node refusal: old /etc/parsar-node records, /var/lib/parsar-node, parsar-node-<id>.service units, ~/.parsar/nodes paths and parsar-node-<id> networks. It also loses the retired PARSAR_NODE_ENROLLMENT_TOKEN check.
  • node_generations.py drops the legacy-unfenced v1 generation marker, and contracts/agents-api/node-generation-protocol.md drops its description.
  • test_node_legacy.py is deleted, along with the legacy cases in test_node_install.py and test_node_generations.py, and the matching scripts/name-allowlist.json entries.

Removal only; current behavior is unchanged. No blind review: a pure deletion, read in full by the coordinator (remaining imports still used, no dangling doc references).

Checks

Focused: make check-distribution (234 installer tests OK, 1 skipped as on main) and make check-names pass. git grep -i -E "parsar|legacy.unfenced|PARSAR_NODE" -- deploy/install/node_* deploy/install/test_node_* finds nothing.

@SaladDay
SaladDay merged commit 7022671 into main Sep 30, 2026
5 checks passed
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