Update adobe.testing.s3mock (major)#3122
Conversation
|
See #3002 (comment) |
ff71252 to
10ed9af
Compare
201ac3e to
16299a1
Compare
16299a1 to
80f7ef9
Compare
65c64f7 to
be50bfb
Compare
9fe82db to
04ab40f
Compare
04ab40f to
30bd1df
Compare
efce4ee to
ae9c9d1
Compare
9d300cc to
b853a85
Compare
2b0746f to
1e40944
Compare
9a1abe3 to
fe1c127
Compare
9a04f5b to
d054730
Compare
762fe16 to
f2cb1bb
Compare
2757fc0 to
ed6f980
Compare
5072a30 to
cad3942
Compare
33c1c40 to
0b9598e
Compare
a396ba9 to
e0d7cfe
Compare
|
This PR has had no activity for 60 days and is now labeled as stale. Any new activity will remove the stale label. To attract more reviewers, please tag people who might be familiar with the code area and/or notify the dev@solr.apache.org mailing list. To exempt this PR from being marked as stale, make it a draft PR or add the label "exempt-stale". If left unattended, this PR will be closed after another 60 days of inactivity. Thank you for your contribution! |
99dd684 to
0d7cdbc
Compare
…mcat licenses s3mock 4.x replaced its embedded Jetty server with Tomcat, which is incompatible with the Java SecurityManager (Tomcat's PrivilegedSetAccessControlContext throws under an SM), causing all s3-repository tests to fail with HTTP 500. Disable the SecurityManager for this test-only module (as extraction/gcs-repository already do). s3mock 4.x also pulls new transitive tomcat-embed-core/-websocket jars; rename the existing tomcat-embed-el LICENSE/NOTICE to the shared 'tomcat-' prefix so they cover all tomcat-embed-* artifacts (all Apache-2.0).
|
Pushed a commit to complete this major upgrade. s3mock 4.x swapped its embedded server from Jetty to Tomcat, which caused two failures:
Verified locally: |
|
@malliaridis Your concern wrt JUnit 5 is not a new concern for s3mock v4. We eventually have to move, but this upgrade can safely be done first. |
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
This PR contains the following updates:
3.12.0→5.1.03.12.0→4.12.4Release Notes
adobe/S3Mock (com.adobe.testing:s3mock-testsupport-common)
v5.1.0Compare Source
initialBucketsentries during startup to avoid creating a bogus root-level persisted bucket.SPRING_PROFILES_ACTIVE=vectors; runs on dedicated HTTP port 9092 / HTTPS port 9193. SupportsCreateVectorBucket,GetVectorBucket,ListVectorBuckets,DeleteVectorBucket,CreateIndex,GetIndex,ListIndexes,DeleteIndex,PutVectors,GetVectors,ListVectors,DeleteVectors,QueryVectors,PutVectorBucketPolicy,GetVectorBucketPolicy,DeleteVectorBucketPolicy,TagResource,UntagResource,ListTagsForResource. See README.md#s3-vectors-support.v5.0.0Compare Source
bucketMetadata.json,objectMetadata.json).Use the current environment variables listed in Configuration instead.
root→ useCOM_ADOBE_TESTING_S3MOCK_STORE_ROOTinitialBuckets→ useCOM_ADOBE_TESTING_S3MOCK_STORE_INITIAL_BUCKETSvalidKmsKeys→ useCOM_ADOBE_TESTING_S3MOCK_STORE_VALID_KMS_KEYSretainFilesOnExit→ useCOM_ADOBE_TESTING_S3MOCK_STORE_RETAIN_FILES_ON_EXITCOM_ADOBE_TESTING_S3MOCK_REGION→ useCOM_ADOBE_TESTING_S3MOCK_STORE_REGIONhttp.port→ use Spring Boot'sSERVER_PORTorcom.adobe.testing.s3mock.httpPortcom.adobe.testing.s3mock.domain.*is no longer supported.Use the
com.adobe.testing.s3mock.store.*prefix instead.com.adobe.testing.s3mock.domain.root→ usecom.adobe.testing.s3mock.store.rootcom.adobe.testing.s3mock.domain.initialBuckets→ usecom.adobe.testing.s3mock.store.initialBucketscom.adobe.testing.s3mock.domain.validKmsKeys→ usecom.adobe.testing.s3mock.store.validKmsKeyscom.adobe.testing.s3mock.domain.retainFilesOnExit→ usecom.adobe.testing.s3mock.store.retainFilesOnExitv4.12.4Compare Source
Version 4.x is JDK17 LTS bytecode compatible, with Docker and JUnit / direct Java integration.
This is the last planned minor release of 4.x.
v4.11.0Compare Source
Version 4.x is JDK17 LTS bytecode compatible, with Docker and JUnit / direct Java integration.
v4.10.0Compare Source
Version 4.x is JDK17 LTS bytecode compatible, with Docker and JUnit / direct Java integration.
v4.9.1Compare Source
Version 4.x is JDK17 LTS bytecode compatible, with Docker and JUnit / direct Java integration.
v4.8.0Compare Source
Version 4.x is JDK17 LTS bytecode compatible, with Docker and JUnit / direct Java integration.
v4.7.0Compare Source
Version 4.x is JDK17 LTS bytecode compatible, with Docker and JUnit / direct Java integration.
v4.6.0Compare Source
Version 4.x is JDK17 LTS bytecode compatible, with Docker and JUnit / direct Java integration.
v4.5.1Compare Source
Version 4.x is JDK17 LTS bytecode compatible, with Docker and JUnit / direct Java integration.
v4.5.0Compare Source
Version 4.x is JDK17 LTS bytecode compatible, with Docker and JUnit / direct Java integration.
v4.4.0Compare Source
Version 4.x is JDK17 LTS bytecode compatible, with Docker and JUnit / direct Java integration.
v4.3.0Compare Source
Version 4.x is JDK17 LTS bytecode compatible, with Docker and JUnit / direct Java integration.
v4.2.0Compare Source
Version 4.x is JDK17 LTS bytecode compatible, with Docker and JUnit / direct Java integration.
v4.1.1Compare Source
Version 4.x is JDK17 LTS bytecode compatible, with Docker and JUnit / direct Java integration.
v4.1.0Compare Source
Version 4.x is JDK17 LTS bytecode compatible, with Docker and JUnit / direct Java integration.
v4.0.0Compare Source
Version 4.x is JDK17 LTS bytecode compatible, with Docker and JUnit / direct Java integration.
DisposableBeaninstead ofFile#deleteOnExit()Configuration
📅 Schedule: (UTC)
* * * * 0)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot