-
Notifications
You must be signed in to change notification settings - Fork 467
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
Experimental custom domain support for ACA. #6275
Merged
Merged
+265
−2
Conversation
This file contains 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
mitchdenny
force-pushed
the
midenn/custom-domains
branch
2 times, most recently
from
October 16, 2024 11:27
efe5257
to
4158361
Compare
mitchdenny
changed the title
Playground with custom domain support.
Experimental custom domain support for ACA.
Oct 17, 2024
mitchdenny
force-pushed
the
midenn/custom-domains
branch
from
October 17, 2024 02:56
4158361
to
4359e24
Compare
davidfowl
reviewed
Oct 17, 2024
davidfowl
reviewed
Oct 17, 2024
mitchdenny
force-pushed
the
midenn/custom-domains
branch
from
October 18, 2024 03:34
4359e24
to
38e0998
Compare
davidfowl
approved these changes
Oct 18, 2024
mitchdenny
force-pushed
the
midenn/custom-domains
branch
from
October 18, 2024 09:07
38e0998
to
70bf98d
Compare
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
davidfowl
reviewed
Oct 18, 2024
throw new ArgumentException("Cannot configure custom domain when resource is not parented by ResourceModuleConstruct.", nameof(app)); | ||
} | ||
|
||
var containerAppManagedEnvironmentIdParameter = module.GetResources().OfType<ProvisioningParameter>().Single( |
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.
I don't love this part.
mitchdenny
force-pushed
the
midenn/custom-domains
branch
from
October 18, 2024 23:58
70bf98d
to
e7b02d1
Compare
mitchdenny
force-pushed
the
midenn/custom-domains
branch
from
October 19, 2024 07:02
efeec27
to
c011637
Compare
mitchdenny
force-pushed
the
midenn/custom-domains
branch
from
October 20, 2024 03:18
a03ea7f
to
07b37a0
Compare
/backport to release/9.0 |
Started backporting to release/9.0: https://github.com/dotnet/aspire/actions/runs/11433206663 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Adds custom domain support to the playground sample. The approach used here is that you deploy first without custom domains enabled (just hit enter on the
certificateName
value but provide the desired custom domain name.Then once you've deployed for the first time go into the portal and go through the binding process for the custom domain and create the appropriate domain ownership verification steps (creating TXT/CNAME records etc).
Once the domain is up and running then you can deploy again, but this time edit the
config.json
file with the name of the certificate (look in the container app environment).Opening this as a PR for now for discussion since we'll probably want to wrap this up in some kind of API. The API would need to augment the callback for configuring the custom domains but also inject parameters for each project its applied to.
Checklist
<remarks />
and<code />
elements on your triple slash comments?Microsoft Reviewers: Open in CodeFlow