Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Used string manipulation instead of templating to remove characters from SAN #15

Closed
wants to merge 1 commit into from

Conversation

mrferos
Copy link

@mrferos mrferos commented Jul 23, 2019

Description

Hi, was experiencing the issue described here

I believe this change creates the list that was being done in the templating, my local testing shows that it no longer errors out but I have not tried the scenarios listed in the issue.

I left the original template bit in as I was just trying to get this working, but can remove it.

@mrferos mrferos changed the title Used some string manipulating to work around the templating Used string manipulation instead of templating to remove characters from SAN Jul 23, 2019
distinct_domain_names = distinct(
concat(
[var.domain_name],
split(":", replace(join(":", var.subject_alternative_names), "*.", ""))
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this should be this instead:

distinct(
  split(":", replace(join(":", concat(var.domain_name, var.subject_alternative_names)), "*.", ""))

Because var.domain_name might also be a wildcard, so that needs to be included in the whole *. filtering.

@jvelasquezjs
Copy link

jvelasquezjs commented Jul 29, 2019

Hi @reegnz , @mrferos

CC: @ezelenka

Can I ask why are we using this distinct_domain_names validation / enforcement? Perhaps I am not able to see the big picture, but IIRC in version 1.4.0 (terraform 11) we used the SAN and domain_name this way?

resource "aws_route53_record" "validation" {

BTW: We are running into the same problem, where planning cannot compute the data source (issue #10)

Thanks!

@jvelasquezjs
Copy link

Please Review PR #16

@bryantbiggs
Copy link
Member

hi @mrferos , @jvelasquezjs - is this still an issue on the latest version of the module or can we close?

@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 15, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants