[CRE-1000] simplify capabilities - add OCR2 keys export fn #2186
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.
Below is a summarization created by an LLM (gpt-4-0125-preview). Be mindful of hallucinations and verify accuracy.
Why
The changes introduce functionality to export OCR2 keys from a Chainlink node's REST client and extend the model to include the structure for the exported OCR2 key. This enhancement allows for better integration and management of OCR2 keys within the Chainlink framework, facilitating operations such as backup, migration, or security auditing.
What
ExportOCR2Key
function to the Chainlink client. This function exports an OCR2 key by its ID, using the Chainlink node's REST API, and includes handling for the response and errors.ExportedOCR2Key
struct to represent the detailed structure of an exported OCR2 key, including cryptographic parameters such as cipher, ciphertext, and key derivation function parameters.