[CRE-1250] Usnet Docker Build Ctx and Filepath if 'CTF_*_IMAGE' env vars are used #2220
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.
Why?
Without this PR TOMLs configs that have docker build ctx/file set will fail, if
CTF_CHAINLINK_IMAGEis used.Below is a summarization created by an LLM (gpt-4-0125-preview). Be mindful of hallucinations and verify accuracy.
Why
The changes ensure that if a Docker image is provided via environment variables for specific components, the Docker build context and file path are unset. This prevents conflicts and ensures that the provided image takes precedence over building a new one.
What
CTF_*_IMAGEenvironment variables are used.NewWithContextfunction to unsetDockerContextandDockerFilePathifCTF_JD_IMAGEenvironment variable is set, ensuring the custom image is used without attempting to build a new one.sharedDBSetupfunction, updated to unsetDockerContextandDockerFilePathfor node specifications ifCTF_CHAINLINK_IMAGEenvironment variable is set, aligning with the approach of using the specified image directly.