You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is probably very difficult to implement given all the different files these could be stored. I am logging it to hear your thoughts and to see if there are possible ways to do this
Background
While using testcontainers, it is common to define docker images using the following syntax:
// Referring directly to an image on Docker Hub (mysql:8.0.24)finalMySQLContainer<?> mysql = newMySQLContainer<>(
DockerImageName.parse("mysql:8.0.24")
)
finalMySQLContainer<?> mysql = newMySQLContainer<>(
DockerImageName.parse("registry.mycompany.com/mirror/mysql:8.0.24")
.asCompatibleSubstituteFor("mysql")
)
It would be ideal if dependabot could detect and update them
if parsing all files is too expensive, maybe we could configure specific files to scan.
The text was updated successfully, but these errors were encountered:
yeikel
changed the title
[Docker] Update testcontainers images used within the codebase
[Docker] Update docker images used within the codebase
Oct 16, 2023
I'm wondering if searching in Properties file can be a good first iteration. I think it is relatively common to extract the versions in these files and it would allow a simpler parsing. We might even force a convention to search for the container value, like container.* or *.container property key.
Is there an existing issue for this?
Feature description
Disclaimer
This is probably very difficult to implement given all the different files these could be stored. I am logging it to hear your thoughts and to see if there are possible ways to do this
Background
While using testcontainers, it is common to define docker images using the following syntax:
It would be ideal if dependabot could detect and update them
if parsing all files is too expensive, maybe we could configure specific files to scan.
The text was updated successfully, but these errors were encountered: