-
Notifications
You must be signed in to change notification settings - Fork 140
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
[bug] fix fastly_tls_subscription resource to properly handle challenges for multi-SAN #435
Conversation
There was a problem hiding this 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.
There was a problem hiding this 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 👍🏼
pushed doc update |
Any chance to get this merged and a release cut? Our workaround is to create separate subscriptions per domain :( |
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. |
Please merge this. Thanks |
Thanks for merging! Can you please cut the 1.0.0 release so consumers can make use of this great work 😃 |
Hi @virgofx this change will actually go into a |
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.