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
Container images used in several tests are currently hard-coded in Java classes. We should have these externalized somehow so that dependabot can update them to ensure the tests stay on current versions of the containers.
Idea 1:
Use a Maven property and a "dummy" dependency of the dependency that dependabot Maven can track for updates. This has the downside of adding a fake dependency and also tracking a version string that may differ from the actual container image tag.
Idea 2:
Add an empty Dockerfile for each image in the test resources that may be loaded and the image reference parsed for use in the tests. The Dockerfiles would be updated automatically by dependabot Docker support. This seems like a better choice than "idea 1".
The text was updated successfully, but these errors were encountered:
Container images used in several tests are currently hard-coded in Java classes. We should have these externalized somehow so that dependabot can update them to ensure the tests stay on current versions of the containers.
Idea 1:
Use a Maven property and a "dummy" dependency of the dependency that dependabot Maven can track for updates. This has the downside of adding a fake dependency and also tracking a version string that may differ from the actual container image tag.
Idea 2:
Add an empty Dockerfile for each image in the test resources that may be loaded and the image reference parsed for use in the tests. The Dockerfiles would be updated automatically by dependabot Docker support. This seems like a better choice than "idea 1".
The text was updated successfully, but these errors were encountered: