feat(appsync): expose the AppSyncDomain of the custom domain of an AppSync api

[AKoetsier]

When configuring a custom domain on an AppSync api you couldn't easily get the AppSyncDomainName attribute of the associated AWS::AppSync::DomainName. This fix will expose that attribute so that the provided example doesn't throw errors.

All Submissions:

• Have you followed the guidelines in our Contributing guide?

Adding new Unconventional Dependencies:

• This PR adds new unconventional dependencies following the process described here

New Features

• Have you added the new feature to an integration test?
  • Did you use yarn integ to deploy the infrastructure and generate the snapshot (i.e. yarn integ without --dry-run)?

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[gitpod-io]

[mrgrain]

Thanks for the contribution!

Let's make the name a bit more user friendly please.

And out of curiosity, what is the difference between appSyncDomainName and the provided domain (myDomainName in the example)?

[mrgrain]

Additionally, please make sure the build is passing. You can see the latest build failure here: #21554 (comment)

tl;dr Your change to the example is not compiling.

[AKoetsier]

And out of curiosity, what is the difference between appSyncDomainName and the provided domain (myDomainName in the example)?

The myDomainName in the example is just the string 'api.example.com'. So the example would create a CNAME with the name api.example.com with a value api.example.com. The appSyncDomainName is the cloudfront url of the newly associated custom domain.

Pull request has been modified.

[mrgrain]

Suggested change

	/**
	* the associated custom AppSync domain, if present
	*
	* @default - no custom associated domain
	*/
	public readonly appSyncDomainName?: string;
	/**
	* The associated domain name provided by AppSync
	*/
	public readonly appSyncDomainName: string;

domainName.attrAppSyncDomainName seems to be always available. Is there a reason why you made this optional at first?

[AKoetsier]

The domainName resource is only created when you pass the domainName properties in the api. So when creating a minimal api it will not create an AWS::AppSync::DomainName or an AWS::AppSync::DomainNameApiAssociation and therefore you don't have the appSyncDomainName.

[mrgrain]

Okay that makes sense. let's update the comment then to make this clear.

[AKoetsier]

Sorry I only just saw this comment appear. I have changed it a bit to be even more clear when you are requesting the appSyncDomainName without a domainName configuration.

Pull request has been modified.

[AKoetsier]

I converted the attribute to a getter function so that we can throw an error when no domainName is configured. This is more inline with other modules and makes it easier to use.

[mrgrain]

I converted the attribute to a getter function so that we can throw an error when no domainName is configured. This is more inline with other modules and makes it easier to use.

Thanks! I was about to comment about that. 😄

[mrgrain]

Looking good now. Ready to ship if the build passes. 🎉

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
• Commit ID: e91882e
• Result: SUCCEEDED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).