[docs] Document automatic HTTPS certificate generation for non-.NET AppHosts#1063
Closed
aspire-repo-bot[bot] wants to merge 1 commit into
Closed
Conversation
…pHosts Documents the new behavior introduced in microsoft/aspire#17454: - When aspire run starts a non-.NET AppHost (e.g., TypeScript) in non-interactive mode and no HTTPS dev certificate exists, the CLI now automatically generates one. - The ASPIRE_CLI_GENERATE_HTTPS_CERTIFICATE environment variable can be set to 'false' to opt out of automatic certificate generation. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
aspire-repo-bot
Bot
added
the
docs-from-code
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents changes from microsoft/aspire#17454 (
@JamesNK).Targeting
release/13.4based on the source PR milestone13.4.Why this PR is needed
PR microsoft/aspire#17454 fixes a failure for non-.NET AppHosts (such as TypeScript AppHosts) where the dashboard resource service defaults to HTTPS but no HTTPS development certificate exists. Unlike .NET projects, TypeScript AppHosts don't trigger the
dotnetfirst-run experience that normally generates the dev cert.The fix adds automatic HTTPS development certificate generation in the Aspire CLI when running a non-.NET AppHost in non-interactive mode, with an opt-out via
ASPIRE_CLI_GENERATE_HTTPS_CERTIFICATE=false.What was changed
Updated
src/frontend/src/content/docs/app-host/certificate-configuration.mdxto document:aspire runASPIRE_CLI_GENERATE_HTTPS_CERTIFICATEenvironment variable opt-out with example commands for bash and PowerShellFiles modified
src/frontend/src/content/docs/app-host/certificate-configuration.mdx— updated existing page