-
Notifications
You must be signed in to change notification settings - Fork 214
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
[Issue] azd doesn't support args with Aspire on project.v0 resource #3678
Comments
This was referenced Apr 10, 2024
ellismg
added a commit
that referenced
this issue
Apr 16, 2024
ellismg
added a commit
that referenced
this issue
Apr 16, 2024
ellismg
added a commit
that referenced
this issue
Apr 16, 2024
davidfowl
referenced
this issue
in prom3theu5/aspirational-manifests
Apr 20, 2024
* Remove placeholder substitution strategies, add JSON expression processing This commit removes all the placeholder substitution strategies and their associated code. Instead, JSON expression processing has been introduced to handle binding replacements and resource connections. Moreover, extensions methods have been added to handle conversion between JSON document and JSON node. Additionally, two new classes namely, ResourceExpressionProcessor and JsonExpressionProcessor have been added to handle evaluations and to resolve JSON expressions respectively. This new approach provides a more flexible and streamlined way to handle resource substitutions and binding. * Update package versions in Directory.Packages.props Several packages have had their versions updated. This includes HandleBars.Net, JsonPath.Net, YamlDotNet, and a few testing-related packages such as TestableIO.System.IO.Abstractions and xunit.runner.visualstudio. These updates should bring improvements and fixes from respective packages.
ellismg
added a commit
that referenced
this issue
Apr 22, 2024
We allow binding expressions to refer to properties of other resources, but we fail if any of these values are secrets (since ACA has no way to treat these as ACA or KeyVault secrets and reference them). If we detect this case, we fail and encourage the user to pass these values via environment variaibles. Fixes #3678
ellismg
added a commit
that referenced
this issue
Apr 22, 2024
We allow binding expressions to refer to properties of other resources, but we fail if any of these values are secrets (since ACA has no way to treat these as ACA or KeyVault secrets and reference them). If we detect this case, we fail and encourage the user to pass these values via environment variaibles. Fixes #3678
ellismg
added a commit
that referenced
this issue
Apr 23, 2024
We allow binding expressions to refer to properties of other resources, but we fail if any of these values are secrets (since ACA has no way to treat these as ACA or KeyVault secrets and reference them). If we detect this case, we fail and encourage the user to pass these values via environment variaibles. Fixes #3678
ellismg
added a commit
that referenced
this issue
Apr 23, 2024
We allow binding expressions to refer to properties of other resources, but we fail if any of these values are secrets (since ACA has no way to treat these as ACA or KeyVault secrets and reference them). If we detect this case, we fail and encourage the user to pass these values via environment variaibles. Fixes #3678
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Output from
azd version
Run
azd version
and copy and paste the output here:Describe the bug
When specifying
args
on a project's manifest, the args aren't getting applied to the ACA container app. For example:To Reproduce
Use an Aspire manifest that has
args
specified for a project.azd init
andazd up
.In the .NET project, log the args to the console:
Expected behavior
When the app starts in ACA, it should log
args: ["one","two","three","ten"]
Actual behavior
Environment
Information on your environment:
* Language name and version: .NET 8
* IDE and version : Visual Studio 17.11 Preview 1
Additional context
Add any other context about the problem here.
cc @vhvb1989 @ellismg
The text was updated successfully, but these errors were encountered: