-
Notifications
You must be signed in to change notification settings - Fork 210
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
Enhance azd init
to auto-detect Dockerfile ARGS and update azure.yaml
#4639
Draft
Menghua1
wants to merge
1
commit into
Azure:main
Choose a base branch
from
Menghua1:fix-issue#4606
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.
Draft
Changes from all commits
Commits
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 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 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 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
Oops, something went wrong.
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.
I wonder if creating an
osutil.ExpandableString
here is the right thing? I think that we probably just want to usestring
(or maybe a structured type that contains the arg name and optional default value). I don't think you'd ever want to callEnvsubst
orMustEnvsubst
on this value since the docker language doesn't think about doing env-var substitution forARG
s.For the docs, it looks like the
ARG
directive in a dockerfile could look like this:ARG foo=${BAR}
Which from my understanding would mean an argument called "foo" with the default value of
${BAR}
.I'm a little worried that when faced with a file like this, we'd end up doing the wrong thing end to end (but I will admit that from the linked issue, I also don't have a great idea of what the expectation is here either).
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.
@ellismg The use of the
osutil.ExpandableString
type to storebuildArgs
is to populate thebuildArgs
configuration in theazure.yaml
file. Later, when parsing theazure.yaml
file,Envsubst()
will be used to replace the environment variable of arg inbuildArgs
.For the ARG instruction
ARG foo=${BAR}
in the Dockerfile, the underlying processing flow of Azd is as follows:If the
foo
arg is not configured in thebuildArgs
in azure.yaml, the bottom layer finally runs thedocker build .
command to build the project. Since--build-arg foo
is not specified, the value offoo
is the defined default value${BAR}
.If the
foo
arg is configured inbuildArgs
in azure.yaml:foo
is hardcode, the Azd bottom layer will build the project by running the commanddocker build . --build-arg foo=xxxxxx
.foo
is the environment variable${AZURE_BAR}
, the environment variable is replaced with the corresponding value, and the Azd bottom layer will finally build the project by runningdocker build . --build-arg foo=xxxxxx
.