-
Notifications
You must be signed in to change notification settings - Fork 707
Add method to emitting env placeholders #9187
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
Conversation
- AsEnvPlaceHolder will add an envrionment variable place holder for docker service/file values. - Unknown parameters become env placeholders
tests/Aspire.Hosting.Docker.Tests/DockerComposePublisherTests.cs
Outdated
Show resolved
Hide resolved
tests/Aspire.Hosting.Docker.Tests/DockerComposePublisherTests.cs
Outdated
Show resolved
Hide resolved
- Updated CapturedEnvironmentVariables to include a source object. - Modified AddEnvironmentVariable method to accept a source parameter. - Adjusted AsEnvironmentPlaceHolder methods to utilize the new source parameter for better context.
… placeholder and update usage in service extensions
| return builder; | ||
| } | ||
|
|
||
| /// <summary> |
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.
@prom3theu5 This is the pattern we want for helm values for the k8s manifest. I am thinking that before we GA either docker compose or the k8s resource types, the underlying model should be more typed so these aren't strings but something like YamlValue<string> (or maybe we go specific and say it's ComposeValue<T> and KubeValue<T>), that way it's type safe.
We need to:
- Allow going from app model to cdk model
- Preserve the association between the cdk value and the aspire app model somewhere (for later)
Description
Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.
Checklist