Closed cduhn17 closed 9 months ago
@cduhn17 - Please note commit a776933, which I created via terraform-docs markdown .
run from the repo directory.
Also, these changes have been applied to COOL production, so you can go ahead and verify them.
I'll need an approval for the record name change and will be following with another changes as I have the production crossfeed cert to create after the api.crossfeed cert is complete. I know clunky, but part of the LE cert creation process.
@cduhn17 - So do you want me to reapply the code with your two most recent commits?
Also, please make your commit messages more specific in the future. "Update file" doesn't give the reader any idea as to the actual changes contained in the commit.
@jsf9k , Yes please. Ill also be sure to be more descriptive with changes. Thanks
@jsf9k , Yes please. Ill also be sure to be more descriptive with changes. Thanks
I just reapplied.
Ok the first one is complete and I have the cert in-hand. Ill be submitting another change for the other record.
@jsf9k , I have added the values that need to be added to proceed with cert generation
@jsf9k , I have added the values that need to be added to proceed with cert generation
I reapplied just now.
@jsf9k @dav3r I have the second certificate. Thanks for all of your help.
@jsf9k @dav3r I have the second certificate. Thanks for all of your help.
OK, so this PR is good to merge now?
๐ฃ Description
We need to update the TXT record for the DNS to create a certificate for Let'sEncrypt. terraform-docs has been run.
Add/Update the api.cyber.dhs.gov TXT, also had to add the TXT record for crossfeed.cyber.dhs.gov
๐ญ Motivation and context
There are no existing ACME certs and these certs will be put in place of current certs
๐งช Testing
Ran terraform-docs to see if any changes were made to the docs
โ Pre-approval checklist