-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(deps): update dependency software.amazon.cryptography:aws-cryptographic-material-providers to v1.7.0 #867
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #867 +/- ##
=========================================
Coverage 77.55% 77.55%
Complexity 966 966
=========================================
Files 97 97
Lines 4531 4531
Branches 422 422
=========================================
Hits 3514 3514
Misses 835 835
Partials 182 182 ☔ View full report in Codecov by Sentry. |
1fc096b
to
b78a6f6
Compare
…raphic-material-providers to v1.7.0 Signed-off-by: mend-for-github.aaakk.us.kg[bot] <mend-for-github.aaakk.us.kg[bot]@users.noreply.github.com>
b78a6f6
to
892e7fe
Compare
The backport to
To backport manually, run these commands in your terminal: # Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/flow-framework/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/flow-framework/backport-2.x
# Create a new branch
git switch --create backport/backport-867-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 973999bf3b055df41029663083ef901f778ac363
# Push it to GitHub
git push --set-upstream origin backport/backport-867-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/flow-framework/backport-2.x Then, create a pull request where the |
…raphic-material-providers to v1.7.0 (opensearch-project#867) Signed-off-by: mend-for-github.aaakk.us.kg[bot] <mend-for-github.aaakk.us.kg[bot]@users.noreply.github.com> Co-authored-by: mend-for-github.aaakk.us.kg[bot] <50673670+mend-for-github.aaakk.us.kg[bot]@users.noreply.github.com>
This PR contains the following updates:
1.0.2
->1.7.0
Release Notes
aws/aws-cryptographic-material-providers-library (software.amazon.cryptography:aws-cryptographic-material-providers)
v1.7.0
Features
v1.6.0
Bug Fixes
:|
(#618) (f12fe5b)Features
1.5.1 (2024-07-08)
Fixes
v1.5.1
Fixes
v1.5.0
Features
v1.4.0
Features
The Hierarchical Keyring's Keystore now supports four (4)
KMSConfigurations
:See our JavaDocs for details
on how these options effect the relationship between
a Keystore and KMS.
Maintenance
v1.3.0
Bug Fixes
Features
1.2.0 (2024-01-08)
Features
Bug Fixes
Maintenance
1.0.2 (2023-10-18)
Bug Fixes
1.0.1 2023-07-26
Fix
VersionKey
Key Store API that no longer checks for the CipherText lengthon the output of a KMS ReEncrypt API call.
1.0.0 2023-07-21
Features
Safe for use in a multi threaded environment,
tries to prevent redundant or overly parallel backend calls.
See Spec changes for details.
Safe for use in a multi threaded environment,
but no extra functionality
BREAKING CHANGES
CreateCryptographicMaterialsCacheInput
now ONLY acceptsCacheType
,which determines which, if any, of the three implemented CMCs will be returned.
DefaultCache
isStormTrackingCache
CreateAwsKmsHierarchicalKeyringInput
:maxCacheSize
fieldcache
field for aCacheType
As such, entries persisted in the Key Store with prior versions of this library are NOT compatibale.
Instead, we recommend Creating a new DynamoDB Table for this version of the Key Store.
CreateKeyInput
now takes:String branchKeyIdentifier
EncryptionContext encryptionContext
encryptionContext
will be added to the Encryption Context sent to KMS prefixed withaws-crypto-ec:
CreateKeyStore
no longer creates a GSIGenerateDataKeyWithoutPlaintext
no longer include's the discarded GSI'sstatus
.Maintenance
Fix
1.0.0-preview-3 2023-06-22
Fix
This simplifies using the cache in concurrent situations.
Rather than having the caller implement some retry logic
the cache will now update the entry.
1.0.0-preview-2 2023-06-19
Fix
1.0.0-preview-1 2023-06-07
Features
This release is considered a developer preview
and is not intended for production use cases.
v1.2.0
Features
Bug Fixes
Maintenance
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.