feat: expand JD memory client functionality to match Job Distributor API#549
Merged
Conversation
🦋 Changeset detectedLatest commit: bf6f4d4 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
This expands the JD memory client functionality to match the Job Distributor API, and updates the test suite.
856e077 to
bf6f4d4
Compare
|
DimitriosNaikopoulos
approved these changes
Oct 30, 2025
Merged
github-merge-queue Bot
pushed a commit
that referenced
this pull request
Nov 3, 2025
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## chainlink-deployments-framework@0.61.0 ### Minor Changes - [#552](#552) [`32b13c5`](32b13c5) Thanks [@ajaskolski](https://github.com/ajaskolski)! - feat: add catalog service integration for datastore operations Features: - Add catalog service support for datastore management as alternative to local file storage - Add `MergeMigrationDataStoreCatalog` method for catalog-based datastore persistence - Existing `MergeMigrationDataStore` method continues to work for file-based storage (no breaking changes) - Add unified `MergeDataStoreToCatalog` function for both initial migration and ongoing merge operations - All catalog operations are transactional to prevent data inconsistencies - Add `DatastoreType` configuration option (`file`/`catalog`) in domain.yaml to control storage backend - Add new CLI command `datastore sync-to-catalog` for initial migration from file-based to catalog storage in CI - Add `SyncDataStoreToCatalog` method to sync entire local datastore to catalog - CLI automatically selects the appropriate merge method based on domain.yaml configuration - Catalog mode does not modify local files - all updates go directly to the catalog service Configuration: - Set `datastore: catalog` in domain.yaml to enable catalog mode - Set `datastore: file` or omit the setting to use traditional file-based storage - CLI commands automatically detect the configuration and use the appropriate storage backend - [#549](#549) [`3e33b93`](3e33b93) Thanks [@jkongie](https://github.com/jkongie)! - Improve JD Memory client to be aligned with the Job Distributor implementation --------- Co-authored-by: app-token-issuer-engops[bot] <144731339+app-token-issuer-engops[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.




This expands the JD memory client functionality to match the Job Distributor API, and updates the test suite.