David Fowler
David Fowler
This is about which configuration section AddParameter looks at (IIUC).
Though I guess now you can do: ``` builder.AddParameter("param", builder.Configuration["ServiceConfiguration:SubService:AzureMaps:Key"]); ```
> Ideally both. During publishing (GH Actions) it would be nice to set Environment variables to satisfy Parameters - in addition to what's been discussed here about their placement in...
I think that changes the feature request. We need to describe the name of the environment variable where this parameter will come from in publish. The default value isn't what...
The problem occurs when default values are secrets. They can't appear in the manifest and that is what this API does. It embeds the default value in the manifest so...
Yes I was thinking of something like this
Undocumented features: https://github.com/Azure/azure-dev/issues/3597
Closing this as not planned
Agree with @IEvangelist. What would you expect the user to do in this situation @geeknoid? Are we missing another abstraction or default implementation?
I don't think this issue includes injecting code. It's about showing client integrations when the detected project type isn't an app host.