Skip to content
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

Use endpoint references for all allocated endpoint resolution #2596

Merged
merged 8 commits into from
Mar 4, 2024

Conversation

davidfowl
Copy link
Member

@davidfowl davidfowl commented Mar 3, 2024

  • Don't use lower level AllocatedEndpointAnnotation directly, instead use EndpointReference to represent the primary endpoint for container resources.
  • Pick a primary named endpoint

Fixes #844

cc @eerhardt I assume this conflicts with your work so putting it up for review so you can see it (built on #2594)

cc @DamianEdwards this is how I assume we'd model parts of the url when trying to build the manifest.

Microsoft Reviewers: Open in CodeFlow

- This change removes setting manifest expressions strings in publish mode (except inputs) and pushes object references into the model directly.
- This change also introduces IManifestExpressionProvider and IValueProvider as way for external code to represent manifest and values without code taking a strong dependendency on it. These are implemented on ParameterResource, IResourceWithConnectionString, EndpointReference and ConnectionStringReference in the core.
- Introduce ConnectionStringReference which stores the underlying resource and an option bool (preserving the syntax of the call itself).
- Added methods on EndpointReference to allow getting various parts of the URL
- BicepOutputReference and BicepSecretOutputReference also implement the new interfaces.
- Use a default endpoint name for the redis endpoint
- Don't use lower level AllocatedEndpointAnnotation directly, instead use EndpointReference to represent the primary endpoint for container resources.
- Pick a primary named endpoint
@dotnet-issue-labeler dotnet-issue-labeler bot added the area-app-model Issues pertaining to the APIs in Aspire.Hosting, e.g. DistributedApplication label Mar 3, 2024
@davidfowl davidfowl added this to the preview 5 (Apr) milestone Mar 3, 2024
@davidfowl davidfowl changed the base branch from davidfowl/references to main March 3, 2024 16:37
@davidfowl
Copy link
Member Author

/azp run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@davidfowl davidfowl merged commit 990f158 into main Mar 4, 2024
8 checks passed
@davidfowl davidfowl deleted the davidfowl/container-endpoints branch March 4, 2024 00:00
@github-actions github-actions bot locked and limited conversation to collaborators Apr 20, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-app-model Issues pertaining to the APIs in Aspire.Hosting, e.g. DistributedApplication
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Change how container connection strings resolve the right endpoint
2 participants