-
-
Notifications
You must be signed in to change notification settings - Fork 587
feat: add the ability to configure the provider type in the properties file or as an env var #3494
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
mkeeler
wants to merge
3
commits into
testcontainers:main
Choose a base branch
from
mkeeler:provider-config
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+186
−7
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
Verify case handling for provider configuration values.
The string comparison for
conf.Provideris case-sensitive. Ensure that the configuration parsing ininternal/config/config.gonormalizes the provider value to lowercase before storing it, otherwise users who setTESTCONTAINERS_PROVIDER=PODMAN(uppercase) might experience unexpected behavior.🏁 Script executed:
Length of output: 371
Now I need to identify which library provides the
propertiestag parsing and whether it handles case normalization.Based on my verification, the original review comment correctly identifies a real case-sensitivity issue. The evidence shows:
From the script output, the environment variable
TESTCONTAINERS_PROVIDERis read directly viaos.Getenv()and assigned toconfig.Providerwithout anystrings.ToLower()call.The switch statement in provider.go (lines 104-109) performs case-sensitive string matching for "docker" and "podman".
The magiconair/properties library used for the
propertiestag does not automatically normalize string values to lowercase—it preserves case as-is.This means if a user sets
TESTCONTAINERS_PROVIDER=PODMAN(uppercase), it won't match the case-sensitive "podman" check and will fall through to the default, causing unexpected behavior.Add case normalization to environment variable assignment in
internal/config/config.go.At line 151, normalize the environment variable to lowercase before assigning it:
This ensures the switch statement in
provider.go(lines 104-109) will correctly match provider values regardless of the case used when setting the environment variable.🏁 Script executed:
Length of output: 723
🏁 Script executed:
Length of output: 163056
Based on the web search results, the magiconair/properties library's string field handling simply returns the string value as-is:
case isString(t): v, err = s, nil. This means the library does NOT normalize string values to lowercase.Verification confirms the original review comment is correct. The case-sensitivity bug exists:
config.Provider = providerEnvAdd case normalization to environment variable assignment in
internal/config/config.go.At line 151, normalize the environment variable to lowercase before assigning it:
This ensures the switch statement in
provider.go(lines 104-109) will correctly match provider values regardless of the case used when setting the environment variable. Without this fix, users settingTESTCONTAINERS_PROVIDER=PODMAN(uppercase, a common practice) will silently have their configuration ignored, with the provider defaulting to Docker instead.🤖 Prompt for AI Agents