chore: bring back testcontainers tests #6957
Open
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.
Hi from the Testcontainers community! 👋
PR Description
This PR bumps the version of Testcontainers for Go, to the latest released: v0.31.0, unskipping all the tests from the code (skipped in #4413).
At the same time, given the project uses testcontainers-go for Vault, I'm including the vault module, in case it's useful.
Which issue(s) this PR fixes
Notes to the Reviewer
I've run the Vault tests locally, even the dev port is using the default in the module (8200/tcp, here it was 80/tcp).
I'm currently checking the existing backlog, and #6670 could conflict with this one, as it keeps some
t.Skip
but not for testcontainers reasons.See https://github.com/grafana/agent/pull/6670/files#diff-1f0f435cab418ca5c8a2e2d6411411bcaf85c131298e21082678de8a33f1adc1R143
PR Checklist