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
{{ message }}
Repository navigation
Replace Bitwarden's private Aspire parameter access with public Aspire 17 APIs #2564
The hosting integration uses four UnsafeAccessor calls into private members of ParameterResource and ParameterProcessor. These calls depend on Aspire's internal parameter state and can break when an Aspire upgrade changes those members.
Aspire 17.0.0 exposes public APIs for this work. Use optional parameters for existing secrets read from Bitwarden. Use Aspire's public parameter APIs to read current values, set resolved values, and prompt for required inputs. Preserve configured values, defaults, and remote prefill when a managed input is missing.
Usage example
Existing AppHost declarations stay the same. bitwarden.AddSecret("managed-key") declares a managed secret. bitwarden.GetSecret("existing-key") reads a secret from Bitwarden without prompting for a local value.
Breaking change?
Existing AppHost signatures stay the same. The hosting package requires Aspire 17.0.0 for the public parameter APIs.
Alternatives
Keep the private accessors and maintain them across Aspire releases.
Additional context
The public parameter APIs landed in microsoft/aspire#18108. This cleanup prepares the integration for the separate resource-output proposal in #1591.
Help us help you
Yes, I'd like to be assigned to work on this item.
Activity