The akamai_property resource provides version attributes latest_version, staging_version, and production_version which makes it possible to conditionally activate either the latest version or keep the version already currently activated on a network.
The akamai_cloudlets_policy resource only provides version attribute version (latest version) so it is not possible to conditionally activate the latest version or a version already currently activated on a network. Either the latest version always has to be activated or a hard-coded version can be activated.
See examples below in "Terraform Configuration Files" section.
Terraform and Akamai Terraform Provider Versions
Terraform v1.9.0
on linux_amd64
+ provider registry.terraform.io/akamai/akamai v6.2.0
akamai_cloudlets_policy resources provide staging and production version attributes (in addition to currently-provided latest version attribute) so activation versions can be conditional.
Actual Behavior
akamai_cloudlets_policy resources only provide the latest version attribute so forced to either always activate latest versions or activate hard-coded versions.
Steps to Reproduce
See examples above in "Terraform Configuration Files" section.
Important Factoids
I have tried using akamai_cloudlets_policy and akamai_cloudlets_shared_policy datasources to dynamically determine activated staging and production versions, but that has been proven unreliable as their activations attribute "empties" when new cloudlet versions are created but not activated right away (perhaps this is a bug in the datasources).
The following data sources should probably provide the same staging and production version attributes as well:
The
akamai_property
resource provides version attributeslatest_version
,staging_version
, andproduction_version
which makes it possible to conditionally activate either the latest version or keep the version already currently activated on a network.The
akamai_cloudlets_policy
resource only provides version attributeversion
(latest version) so it is not possible to conditionally activate the latest version or a version already currently activated on a network. Either the latest version always has to be activated or a hard-coded version can be activated.See examples below in "Terraform Configuration Files" section.
Terraform and Akamai Terraform Provider Versions
Affected Resource(s)
akamai_cloudlets_policy
Terraform Configuration Files
Cloudlet activate latest version example:
Cloudlet activate hard-coded version example:
Property activate conditional version example:
Debug Output
N/A
Panic Output
N/A
Expected Behavior
akamai_cloudlets_policy
resources provide staging and production version attributes (in addition to currently-provided latest version attribute) so activation versions can be conditional.Actual Behavior
akamai_cloudlets_policy
resources only provide the latest version attribute so forced to either always activate latest versions or activate hard-coded versions.Steps to Reproduce
See examples above in "Terraform Configuration Files" section.
Important Factoids
I have tried using
akamai_cloudlets_policy
andakamai_cloudlets_shared_policy
datasources to dynamically determine activated staging and production versions, but that has been proven unreliable as theiractivations
attribute "empties" when new cloudlet versions are created but not activated right away (perhaps this is a bug in the datasources).The following data sources should probably provide the same staging and production version attributes as well:
akamai_cloudlets_policy
akamai_cloudlets_shared_policy
References
N/A