billowy-laptop-4596304/19/2021, 12:12 AM
is that correct?
bored-oyster-314704/19/2021, 12:32 AM
billowy-laptop-4596304/19/2021, 1:13 AM
bored-oyster-314704/19/2021, 12:49 PM
billowy-laptop-4596304/19/2021, 1:29 PM
bored-oyster-314704/19/2021, 1:39 PM
. And if you know the order your domains should be in after sorting than you would know at which indices in the array you need to provide which providers. But I don't think there is way to have a setup such that when you update the cert by adding a new domain name you will only have to update 1 validation record. Because even if you sorted it this new domain could end up in the middle of your sorted array so every record that came after it would need to be recreated as well (because presumably your naming the resources by index or something). Alternatively if it is an option for you, I don't think it really costs anything or too much to make additional ACM certs for your AWS infrastructure. Is it possible for you to make separate certs? Then your separate provider issue would be trivial.
var sortedOptions = options.apply(unsorted => ........ return sorted);
billowy-laptop-4596304/19/2021, 1:43 PM
bored-oyster-314704/19/2021, 1:44 PM
on the domain validation options right? And I'm pretty sure resource name only accepts
. Or was that not giving you compile errors because you were doing it inside of an
so it was a
billowy-laptop-4596304/19/2021, 1:46 PM
validations = [domainName, ...subjectAlternativeNames]
bored-oyster-314704/19/2021, 1:48 PM
billowy-laptop-4596304/19/2021, 1:51 PM
and when I loop over validations to create the records the index should match up?
validations = [domainName, ...subjectAlternativeNames].sort() options = cert.domainValidationOptions.apply(//sort)
bored-oyster-314704/19/2021, 1:52 PM
billowy-laptop-4596304/19/2021, 1:54 PM
bored-oyster-314704/19/2021, 1:56 PM