(OraklNode) Signer auto renewal

[nick-bisonai]

Description

PGSQL encrypted load and store

Type of change

Please delete options that are not relevant.

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] This change requires a documentation update

Checklist before requesting a review

• [x] I have performed a self-review of my code.
• [ ] If it is a core feature, I have added thorough tests.

Deployment

• [ ] Should publish npm package
• [x] Should publish Docker image

[coderabbitai[bot]]

Walkthrough

## Walkthrough The recent changes introduce a new Signer mechanism to the Node application for enhanced signing and verification of data. The changes span across migrations to add new `signer` tables, modifications in the `aggregator` package to utilize the new Signer context, and updates in the `helper` package for managing signer keys and configurations. Testing files have been adjusted to incorporate these new structures and functionalities. ## Changes | File(s) | Summary | |--------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------| | `node/migrations/node/...signer.*.sql` | Added migrations to create and drop the `signer` table with columns `id`, `pk`, and `unique_dummy`. | | `node/pkg/aggregator/aggregator.go` | Enhanced `NewAggregator` to accept `context.Context` and `helper.Signer`, updating the struct accordingly. | | `node/pkg/aggregator/..._test.go` | Modified test functions to include the `signer` parameter in `NewAggregator` calls. | | `node/pkg/aggregator/app.go` | Adjusted `initializeLoadedAggregators` to accept `context.Context` and use Signer configuration options. | | `node/pkg/aggregator/types.go` | Renamed `SignHelper` field to `Signer` in the `Aggregator` struct. | | `node/pkg/chain/helper/helper.go` | Modified `NewSignHelper` to load and store signer keys using context and added error handling. | | `node/pkg/chain/helper/signer.go` | Introduced the `helper` package for Signer management, including key updates, renewal checks, and configurations. | | `node/pkg/chain/helper/types.go` | Updated `Signer` struct fields and added constants for renewal intervals and function signatures. | | `node/pkg/chain/tests/chain_test.go` | Adjusted `NewSignHelper` calls to include context and added tests for signer key generation and renewal. | | `node/pkg/chain/utils/utils.go` | Added functions to load, store, and generate signer keys. | | `node/pkg/error/sentinel.go` | Introduced custom error variables for contract handling. | | `node/pkg/.../main_test.go` | Updated `helper.NewSignHelper` calls to include the context parameter. | | `node/pkg/fetcher/main_test.go` | Added a deletion query before inserting sample data in tests. | ## Poem > Beneath the code, where bytes do play, > A Signer leaps, in bright array. > With keys it guards and secrets keeps, > New functions bloom where silence sleeps. > Tests aligned in thoughtful form, > Ensuring all is safe and warm. > Oh, how our code does sing today! ``` (\(\ ( -.-) o_(")(") ```

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

- [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit .` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai generate interesting stats about this repository and render them as a table.` - `@coderabbitai show all the console.log statements in this repository.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` - `@coderabbitai help me debug CodeRabbit configuration file.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (invoked as PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger an incremental review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai full review` to do a full review from scratch and review all the files again. - `@coderabbitai summary` to regenerate the summary of the PR. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository. - `@coderabbitai help` to get help. Additionally, you can add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. ### CodeRabbit Configration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information. - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json` ### Documentation and Community - Visit our [Documentation](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.