Skip to content
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

Bump testcontainers-keycloak from 1.9.0 to 2.2.1 #63

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github May 2, 2022

Bumps testcontainers-keycloak from 1.9.0 to 2.2.1.

Release notes

Sourced from testcontainers-keycloak's releases.

2.2.0: Keycloak 18 Support

  • upgrade Keycloak Docker image to 18.0.0
  • using the again-available --import-realm option, thus removing the manual approach with the keycloak-admin-client, less code to maintain
  • use the start-dev mode again, as it makes no difference in using this compared to use all the other single commands and it's easier to maintain

2.1.2: Bug fixes / maintenance

  • Don't rely on Maven directory when building temporary extension deployment (will enable usage with Gradle etc.).
  • Don't try to re-import a realm when a container is reused.
  • Use Thread.currentThread().getContextClassLoader() in certain cases for importing realm files (will be removed completely again, as soon Keycloak supports auto-import of realms again)
  • Upgrade to Keycloak 17.0.1

2.1.1: Revert RestEasy version changes

The dependency version changes in release 2.1.0 were wrong... blame on me! This release revert these changes again.

2.1.0: Ability to add external libraries

Don't use this version!!! Use 2.1.1 instead!!!


Changes

The auto-build flag is now used always, not matter if really needed or not. This makes adding custom resources which need a build before a lot easier. The most use cases need a build anyway, so this shouldn't matter that much.

Fixes

The Java Admin Client now uses RestEasy dependency versions aligned with the Keycloak runtime. Before, this could lead to a version clash and exceptions during runtime, if you were using different versions in your tests.

New Features

It's now possible to add 3rd party libs, like e.g. further dependencies or other files, to your KeycloakContainer /providers folder with the new .withProviderLibsFrom(...) method. See README.md for further details and also a linked example for how to add dependencies from your maven pom.xml

Keycloak 17 support (Quarkus-based distribution)

Breaking Changes

  • The new base image is the Quarkus-based distribution of Keycloak This version branch WILL NOT work with legacy (Wildfly-based) Keycloak distributions!
  • if you used withExtensionClassesFrom(), you have to change it to withProviderClassesFrom() method
  • the URL returned by getAuthServerUrl() now has a trailing /, possibly you have to change the way you construct/concatenate your paths, you can adjust your custom context path with .withContextPath(...)

New Features

  • the Keycloak admin client org.keycloak:keycloak-admin-client is now a transitive dependency of this library and can be used right out of the box by calling keycloakContainer.getKeycloakAdminClient().
  • you can adjust your custom context path with .withContextPath(...)
  • additionally to TLS config with certificate and key file, you can now use a ready built Java keystore with .useTlsKeystore(keystoreFilename, keystorePassword)
  • you can enable/disable Keycloak features with .withFeaturesEnabled(features...) and .withFeaturesDisabled(features...)

Other Changes

... (truncated)

Commits
  • 1666d50 [maven-release-plugin] prepare release 2.2.1
  • 44d4537 adjust expected test duration to changed defaults
  • ba20cfc Allow import realm files from directories (#74)
  • ebbbaa8 [maven-release-plugin] prepare for next development iteration
  • 01923c5 [maven-release-plugin] prepare release 2.2.0
  • 140ad65 upgrade restassured to most recent version
  • 6061ea4 upgrade to KC 18.0.0
  • 1e86de1 close keycloak admin client (#69)
  • fc1da13 github issue templates
  • 660b7a2 [maven-release-plugin] prepare for next development iteration
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label May 2, 2022
@dependabot dependabot bot requested a review from lmsurpre May 2, 2022 05:19
@dependabot dependabot bot force-pushed the dependabot/maven/com.github.dasniko-testcontainers-keycloak-2.2.1 branch from 291898b to 406091a Compare May 2, 2022 16:17
Bumps [testcontainers-keycloak](https://github.com/dasniko/testcontainers-keycloak) from 1.9.0 to 2.2.1.
- [Release notes](https://github.com/dasniko/testcontainers-keycloak/releases)
- [Commits](dasniko/testcontainers-keycloak@1.9.0...2.2.1)

---
updated-dependencies:
- dependency-name: com.github.dasniko:testcontainers-keycloak
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot force-pushed the dependabot/maven/com.github.dasniko-testcontainers-keycloak-2.2.1 branch from 406091a to c885598 Compare May 2, 2022 18:00
@lmsurpre
Copy link
Collaborator

lmsurpre commented May 2, 2022

testcontainers-keycloak is only compatible with the newer quarkus-based distribution. we now have #64 for that.

@dependabot ignore this major version

@lmsurpre lmsurpre closed this May 2, 2022
@dependabot dependabot bot deleted the dependabot/maven/com.github.dasniko-testcontainers-keycloak-2.2.1 branch May 2, 2022 18:11
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github May 2, 2022

OK, I won't notify you about version 2.x.x again, unless you re-open this PR or update to a 2.x.x release yourself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant