Skip to content

Conversation

@FlorinPeter
Copy link

Implement ExtendNodeExpiration RPC, allowing users to extend a node's expiration. Update the CLI to include the extend-expiration command with required fields. Validate inputs, update the database, and notify peers of expiration changes.

  • have read the CONTRIBUTING.md file
  • raised a GitHub issue or discussed it on the projects chat beforehand
  • added unit tests
  • added integration tests
  • updated documentation if needed
  • updated CHANGELOG.md

@kradalby
Copy link
Collaborator

Apologies for missing this among other PRs and work, can you rebase this? It will need some integration tests tho to validate that the expected behaviour happens.

@FlorinPeter FlorinPeter force-pushed the add-extend-expiration branch from c73ba08 to 3689639 Compare July 23, 2025 08:12
@ghost
Copy link

ghost commented Jul 23, 2025

Pull Request Revisions

RevisionDescription
r2
Node expiration extension enhancedAdded expiration validation, maximum 2-year limit, and improved node expiry extension process with policy change handling
r1
Added node expiration extension commandImplemented new gRPC endpoint and CLI command to extend node expiration with new-expiry flag

✅ AI review completed for r2
Help React with emojis to give feedback on AI-generated reviews:
  • 👍 means the feedback was helpful and actionable
  • 👎 means the feedback was incorrect or unhelpful
💬 Replying to feedback with a comment helps us improve the system. Your input also contributes to shaping future interactions with the AI reviewer.

We'd love to hear from you—reach out anytime at team@review.ai.

This commit adds the ability to extend node expiration through both
gRPC API and CLI commands, including:

- New gRPC ExtendNodeExpiration method with validation
- CLI extend-expiration command with proper error handling
- Expiration upper bound validation (max 2 years from current time)
- Updated generated protobuf files with proper body consumption
- Appropriate notifications for expiration changes
@FlorinPeter FlorinPeter force-pushed the add-extend-expiration branch from 3689639 to c9d7f25 Compare July 23, 2025 08:30
@FlorinPeter
Copy link
Author

@kradalby sorry the message was drowned in my inbox, it is rebased now

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.

2 participants