CNAMEAlreadyExists issue with enableCloudFront

[rokoroku]

When combining with cloundFront options, only the first run success, and other run fails with following error:

CNAMEAlreadyExists: One or more of the CNAMEs you provided are already associated with a different resource.
    at Request.extractError (/Users/rok/WebstormProjects/closer-landing-page/node_modules/aws-sdk/lib/protocol/rest_xml.js:53:29)
    at Request.callListeners (/Users/rok/WebstormProjects/closer-landing-page/node_modules/aws-sdk/lib/sequential_executor.js:105:20)
    at Request.emit (/Users/rok/WebstormProjects/closer-landing-page/node_modules/aws-sdk/lib/sequential_executor.js:77:10)
    at Request.emit (/Users/rok/WebstormProjects/closer-landing-page/node_modules/aws-sdk/lib/request.js:673:14)
    at Request.transition (/Users/rok/WebstormProjects/closer-landing-page/node_modules/aws-sdk/lib/request.js:22:10)
    at AcceptorStateMachine.runTo (/Users/rok/WebstormProjects/closer-landing-page/node_modules/aws-sdk/lib/state_machine.js:14:12)
    at /Users/rok/WebstormProjects/closer-landing-page/node_modules/aws-sdk/lib/state_machine.js:26:10
    at Request.<anonymous> (/Users/rok/WebstormProjects/closer-landing-page/node_modules/aws-sdk/lib/request.js:38:9)
    at Request.<anonymous> (/Users/rok/WebstormProjects/closer-landing-page/node_modules/aws-sdk/lib/request.js:675:12)
    at Request.callListeners (/Users/rok/WebstormProjects/closer-landing-page/node_modules/aws-sdk/lib/sequential_executor.js:115:18)

Is there any configuration points that we can specify CF distribution ID or something else?

[nick-benoit14]

@rokoroku Can you elaborate a bit on what you mean by combining cloudFront options? Is the happening when you re-run the create command?

[rokoroku]

Ah, yes, I was re-run the create command.
I'll try deploycommand after create the cloundfont options

[nick-benoit14]

@rokoroku Currently I don't believe re-creating the cloudfront domain will work. I am absolutely open to a pull request that would support that though. It may be as simple as checking to see if the cloud front domain has already been configured before attempting to create it again.