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

[bug] fix fastly_tls_subscription resource to properly handle challenges for multi-SAN #435

Merged
merged 8 commits into from
Jul 20, 2021

Conversation

smaeda-ks
Copy link
Contributor

@smaeda-ks smaeda-ks commented Jun 27, 2021

fix for: #430

Looks like when this resource was originally implemented, multi-SAN cert subscription wasn't taken into account. Specifically, this part...
https://github.com/fastly/terraform-provider-fastly/blob/v0.32.0/fastly/resource_fastly_tls_subscription.go#L176

Therefore, the state file only includes the first domain's challenge data, which is a bug.

Though this is definitely going to be a breaking change.

@smaeda-ks smaeda-ks changed the title [bug] fix fastly_tls_subscription resource to properly handle DNS challenges for multi-SAN [bug] fix fastly_tls_subscription resource to properly handle challenges for multi-SAN Jun 28, 2021
Copy link
Collaborator

@Integralist Integralist left a comment

Choose a reason for hiding this comment

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

This looks OK to me, but we don't want to merge this until we've discussed a major 1.0.0 release (@smaeda-ks I'll be having discussions with @bengesoff about 1.0.0 as part of our Q3 goals).

In the mean time I'd also want to get @bengesoff's approval of these changes too.

Copy link
Contributor

@bengesoff bengesoff left a comment

Choose a reason for hiding this comment

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

Think make generate-docs needs rerunning, but otherwise LGTM 👍🏼

@smaeda-ks
Copy link
Contributor Author

pushed doc update

@virgofx
Copy link
Contributor

virgofx commented Jul 13, 2021

Any chance to get this merged and a release cut? Our workaround is to create separate subscriptions per domain :(

@Integralist
Copy link
Collaborator

Hi @virgofx the current implementation is considered a breaking change and so would need to be part of a 1.0.0 release (something we're actively working towards at the moment, but unfortunately I couldn't say with certainty as to when exactly it would be ready to release).

In the meantime I'm discussing with the team potential workarounds that don't result in a breaking change.

@smaeda-ks
Copy link
Contributor Author

Please merge this. Thanks

@Integralist Integralist merged commit d810875 into fastly:main Jul 20, 2021
@virgofx
Copy link
Contributor

virgofx commented Jul 22, 2021

Thanks for merging! Can you please cut the 1.0.0 release so consumers can make use of this great work 😃

@Integralist
Copy link
Collaborator

Hi @virgofx this change will actually go into a 0.33.0 release. We're actively fixing some broken integration tests at the moment, but once we have those fixed I'll be cutting that new release 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants