As of today, we can only load local artifacts coming from the project structure (and loaded as a classpath resource). Because Microcks promotes reusing shared artifacts, we should also be able to load remote HTTP(S) artifacts within our Testcontainers module.
Description
Provide a withMainRemoteArtifacts(String... artifactsUrl) and a withSecondaryRemoteArtifacts(String... artifactsUrl) methods to allow loading remote artifacts just after the container startup.
Implementation ideas
This method may reuse the /api/artifact/download API endpoint of the running Microcks container.
Reason/Context
As of today, we can only load local artifacts coming from the project structure (and loaded as a classpath resource). Because Microcks promotes reusing shared artifacts, we should also be able to load remote HTTP(S) artifacts within our Testcontainers module.
Description
Provide a
withMainRemoteArtifacts(String... artifactsUrl)
and awithSecondaryRemoteArtifacts(String... artifactsUrl)
methods to allow loading remote artifacts just after the container startup.Implementation ideas
This method may reuse the
/api/artifact/download
API endpoint of the running Microcks container.