Skip to content

Release: Jira diff output, attribute preservation, RADb mirroring, and housekeeping#3

Merged
VegasNative merged 5 commits into
mainfrom
develop
May 5, 2026
Merged

Release: Jira diff output, attribute preservation, RADb mirroring, and housekeeping#3
VegasNative merged 5 commits into
mainfrom
develop

Conversation

@VegasNative
Copy link
Copy Markdown
Collaborator

Summary

  • Jira diff output: Changes print as a {code:diff} block with +/-/ prefixes, ready to paste into a Jira comment
  • Attribute preservation on update: Unmanaged attributes (remarks, admin-c, tech-c, etc.) are preserved when updating route objects across all three registries
  • Automatic RADb mirroring: RIPE and ARIN route changes (create, update, delete) cascade to RADb when a radb section is configured
  • delete: true support for RIPE: Route objects can be declaratively deleted; deletions mirror to RADb
  • Code of Conduct: Added CODE_OF_CONDUCT.md
  • config.example.yaml: Annotated example covering all three registries, including delete, max_length, and RADb mirroring behaviour

Test plan

  • 87 unit tests pass (uv run pytest)
  • Ruff lint and format check pass

Replaces per-route print statements with a Summary collector that emits a
{code:diff} block at the end of each run. Created routes render green (+),
deleted routes render red (-), and updated routes appear as neutral context
lines. Dry-run mode is indicated in the header and uses the same prefixes
to show what would change.

Client dry-run return values are now 'dry-run-create', 'dry-run-update',
and 'dry-run-delete' so callers can distinguish the intended operation.
…to RADb

- Replace exists-check with full fetch on update so existing unmanaged attributes
  (remarks, admin-c, tech-c, etc.) are preserved in PUT/update payloads
- Add delete_route() to RIPE, ARIN, and RADb clients
- Mirror every RIPE and ARIN route change (create/update/delete) to RADb
  automatically when a radb section is present in the config
- Skip RADb-only routes that were already mirrored to avoid double-syncing
- Document delete:true flag, automatic mirroring, and attribute preservation in README
Public repo in one of Mozilla’s GH Orgs should include their Code of Conduct file.
@VegasNative VegasNative merged commit f3fa1a4 into main May 5, 2026
1 check 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