Upsert records to the Copilot-managed hosted zone if http.alias
is detected to be a managed subdomain
#5456
Labels
type/enhancement
Issues that are improvements for existing features.
There are a lot of ways to enable an alias in
http.alias
:app init --domain example.com
. Any service in the application will be able to use, at least example.com, *.example.com, *.app.example.com.Scenario 2 and 3 requires users to upsert the A records for their alias on their own, OR specify the
hosted_zone
field so that Copilot knows where to upsert the records.It'd be an UX improvement if Copilot can tell if the
http.alias
is one of the domain enabled in scenario 1 (i.e. example.com, *.example.com, *.app.example.com), and upsert the A records to the respective hosted zone automatically without needing thehttp.hosted_zone
field.Related: #5438
The text was updated successfully, but these errors were encountered: