-
Notifications
You must be signed in to change notification settings - Fork 101
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
DXE-2805 terrform import akamai_edge_hostname not importing certificate #338
Comments
Hello @BAu0002, Thanks and best regards, |
resource "akamai_edge_hostname" "hostname" { |
I ran into the same issue. To work around it, I pulled the state, manually edited it, and pushed it back up. To have a terraform plan see
|
We dropped product id and certificate from import. Also tested and seems to be repaired in scope of issue ip_behavior. |
I'm currently creating some Akamai Terraform modules and have come across this for the Initially I ran into the same must be replaced issue which led me here. As @mimazaka mentioned, after pulling the state locally I can see
My original implementation set Setting |
Hi @james-downing, thank you for pointing it out. It seems that there are still some issues on this resource. We need some time for investigation and will get back to you soon. Best regards, |
I think this bug is likely related to the issue I ran into today. I created edge hostname resources referencing an old certificate which was not to be used for this edge hostname. We don't manage the certifiicates in terraform for now. When updating the edge hostname resource, I got this during plan:
I see that the edge hostname is still using the old certificate. |
Similarly to what @vegardengen noticed, we recently had the requirement of creating new edge hostnames while still managing imported hostnames. Obviously this isn't possible when setting:
By setting the correct |
This is definitely causing a problem for us. Without the product and certificate in the import, the EHN wants to replace when we update the contacts on the certificate. An EHN provisioned by the TF does show the cert and product in the state, so we would expect the import to bring those fields in as well. How should we go about solving this? |
bump. This is also a PITA for us. Though the ehn destroy/create is fast enough, it always results in a change notice for us, indicating that something changed. |
There were some changes in this area that should make things more clear: |
In testing this on v6.0.0, the validations make the issue worse. The Preliminary testing on 5.6.0 was leaning towards the EHNs not actually regenerating thus not actually forcing a replacement like the plan was saying. So, fixing it from detecting a drift was one option. We were waiting to confirm our suspicions and could run the However, I do like the validation method. The only thing is we need import of EHNs to bring in those two fields, otherwise the validation will trigger immediately upon import, and there's no workaround for us. I have attempted both a We need a way for Please advise. Thanks! CC: @aka-mark |
Re-opening to review updated comments. |
I'm trying to import an Enhanced TLS edge hostname.
I ran a code like:
terraform import akamai_edge_hostname.example ehn_123,ctr_1-AB123,grp_123
When I run plan it show's the resource going to be deleted and reconstructed.
akamai_edge_hostname.hostname must be replaced
-/+ resource "akamai_edge_hostname" "hostname" {
+ certificate = # forces replacement
~ contract = "ctr_1-AB123" -> (known after apply)
~ group = "grp_123" -> (known after apply)
~ id = "ehn_123" -> (known after apply)
...
}
Am I missing something?
The text was updated successfully, but these errors were encountered: