KMS Instance Policies not setting key_create_import_access values correctly

[MatthewLemmond]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform CLI and Terraform IBM Provider Version

Terraform v1.3.7
on darwin_amd64

• provider registry.terraform.io/ibm-cloud/ibm v1.50.0

Affected Resource(s)

• ibm_kms_instance_policies

Terraform Configuration Files

Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.

resource "ibm_resource_group" "resource_group" {
  name = "tmp-resource-group"
}

resource "ibm_resource_instance" "key_protect_instance" {
  name              = "tmp-kp"
  resource_group_id = ibm_resource_group.resource_group.id
  service           = "kms"
  plan              = "tiered-pricing"
  location          = "eu-gb"
  service_endpoints = "public-and-private"
}

resource "ibm_kms_instance_policies" "key_protect_instance_policies" {
  instance_id = ibm_resource_instance.key_protect_instance.guid
  key_create_import_access {
    enabled             = true
    create_root_key     = true
    create_standard_key = false
    import_root_key     = true
    import_standard_key = false
    enforce_token       = false
  }
}

Debug Output

https://gist.github.com/MatthewLemmond/c9b8d469fb807cfba51293e97eb3d880

Panic Output

N/A

Expected Behavior

Expected the call to set the instance policy for key create import access according to the values passed in.

Actual Behavior

Values for the key create import access policy were set to their defaults.

Steps to Reproduce

1. tf apply

Important Factoids

References

• #0000

[ocofaigh]

@hkantare Any idea who could look into this?

[hkantare]

@ocofaigh The people for KMS team can look into this
@dinesh-venkatraman (dinesh.venkatraman@in.ibm.com)
Harshit Gupta (harshit.gupta2@ibm.com)

[hkantare]

@ocofaigh The support for KMS is now handled by KMS team (US team)
Bruno Henriques (bruno.henriques@ibm.com) can you please take this issue with the team?

[ocofaigh]

Thanks, I have reached out to Bruno

[BrunoHenriques]

PR with the fix at #4467

[ocofaigh]

@BrunoHenriques If this is now fixed, can you confirm which version of the provider and perhaps close the issue?

[BrunoHenriques]

@BrunoHenriques If this is now fixed, can you confirm which version of the provider and perhaps close the issue?

@ocofaigh

Fixed as part of IBM-Cloud/terraform-provider v1.53.0
See https://github.com/IBM-Cloud/terraform-provider-ibm/releases/tag/v1.53.0.

[BrunoHenriques]

@MatthewLemmond Please verify the fix using IBM-Cloud/terraform-provider v1.53.0 can close the issue. Thank you.

[MatthewLemmond]

Confirmed, this issue is now resolved, closing this out