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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump toxiproxy from 1.16.3 to 1.17.0 #174

Merged
merged 1 commit into from
Apr 13, 2022

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Apr 12, 2022

Bumps toxiproxy from 1.16.3 to 1.17.0.

Release notes

Sourced from toxiproxy's releases.

1.17.0

What's Changed

Highlights

This new version of Testcontainers comes packed with many new features and quality-of-life improvements, so we appropriately bumped the version to 1.17.0.

馃悵 New Module: HiveMQ (#4797) @鈥媃annickWeber

Having started its Open Source life as its own 3rd-party Testcontainers library, we are very happy to welcome HiveMQ into the main repository. Now, using HiveMQ as part of your integration tests is as simple as a couple of lines of Java code:

@Container
HiveMQContainer hivemq = new HiveMQContainer(DockerImageName.parse("hivemq/hivemq-ce:2021.3"));
hivemq.start();
Mqtt5BlockingClient client = Mqtt5Client.builder()
.serverPort(hivemqCe.getMqttPort())
.serverHost(hivemqCe.getHost())
.buildBlocking();
client.connect();

Check out the docs to learn more about its many features!

馃拃 Ryuk JVM mode (#4959) (#4960) @鈥媌sideup

Many Testcontainers user love the convenience Ryuk brings to Testcontainers: No matter what you do in your integration tests, Ryuk has got you covered and will cleanup all Docker resources created by Testcontainers after your test run is finished.

But some users operate Testcontainers in environments which do not support our container-based Ryuk implementation. So far their only option was to disable Ryuk alltogether.

Coming with this release, Testcontainers will now fallback to a JVM based resource-cleanup implementation in case of Ryuk being disabled. While this won't be as robust as the Ryuk container based implementation in all circumstances, it is nevertheless a great addition and acts as a useful compromise.

馃殌 Features & Enhancements

... (truncated)

Commits
  • 17407ef Increase default client ping timeout from 5 to 10 seconds (#5254)
  • d93dcea Allow to create a file in container from a Transferable (#3814) (#3815)
  • c7449ed Elasticsearch: Ensure Elasticsearch 8 works OOTB secure as default (#5099)
  • 53e80aa Fix incorrect path for RABBITMQ_CONFIG_FILE (#5184)
  • 734678f Deperecate getContainerIpAddress (#5247)
  • aed4476 Merge pull request #5248 from testcontainers/combined-pr-branch
  • ae6bc93 Merge remote-tracking branch 'origin/dependabot/github_actions/actions/checko...
  • 30fa262 Merge remote-tracking branch 'origin/dependabot/gradle/modules/jdbc-test/org....
  • 8575add Merge remote-tracking branch 'origin/dependabot/gradle/modules/jdbc/org.apach...
  • cb4fb88 Merge remote-tracking branch 'origin/dependabot/gradle/modules/neo4j/org.neo4...
  • 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)

Bumps [toxiproxy](https://github.com/testcontainers/testcontainers-java) from 1.16.3 to 1.17.0.
- [Release notes](https://github.com/testcontainers/testcontainers-java/releases)
- [Changelog](https://github.com/testcontainers/testcontainers-java/blob/master/CHANGELOG.md)
- [Commits](testcontainers/testcontainers-java@1.16.3...1.17.0)

---
updated-dependencies:
- dependency-name: org.testcontainers:toxiproxy
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Copy link
Contributor

@smcvb smcvb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me 馃憤

@sonarcloud
Copy link

sonarcloud bot commented Apr 13, 2022

Kudos, SonarCloud Quality Gate passed!聽 聽 Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@smcvb smcvb merged commit a761496 into master Apr 13, 2022
@dependabot dependabot bot deleted the dependabot/maven/org.testcontainers-toxiproxy-1.17.0 branch April 13, 2022 10:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant