You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[release/9.1] Hide secrets in source tooltip, correct ExpressionResolver logic for non-containers (#7708)
* Replace tuple with record type in source view model, hide secrets in tooltip
* Remove sourceIsContainer checks in ResolveInternalAsync
* Fix test
* EndpointReference/Expression need to only be container
* Apply suggestion
* special case ResourceWithConnectionStringSurrogate
* Update comment
* Fix discrepant behavior between ReferenceExpression.GetValueAsync and ExpressionResolver.EvalExpressionAsync
* Invoke GetValueAsync on ConnectionStringReference before resolving it, to prevent non-optional but missing value from resolving
* Update src/Aspire.Hosting/ApplicationModel/ExpressionResolver.cs
Co-authored-by: James Newton-King <[email protected]>
* Improve comment in ResolveConnectionStringReferenceAsync
* Change DashboardUIHelpers.GetMaskingText to return a record
* clean up ResourceSourceViewModel
* add additional secrets in test case
* Add additional ExpressionResolver tests
---------
Co-authored-by: Adam Ratzman <[email protected]>
Co-authored-by: Dan Moseley <[email protected]>
Co-authored-by: James Newton-King <[email protected]>
/// Resolve an expression when it is being used from inside a container.
153
-
/// So it's either a container-to-container or container-to-exe communication.
165
+
/// Resolve an expression. When it is being used from inside a container, endpoints may be evaluated (either in a container-to-container or container-to-exe communication).
IResourceWithConnectionStringcs and not ResourceWithConnectionStringSurrogate=>awaitResolveInternalAsync(cs.ConnectionStringExpression).ConfigureAwait(false),
0 commit comments