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

[FEAT] Support notaction argument in alicloud_ram_policy_document Data sources #7444

Open
songhd opened this issue Jul 11, 2024 · 0 comments

Comments

@songhd
Copy link

songhd commented Jul 11, 2024

Description

When using the Alicloud Terraform provider to manage resources on the Alibaba Cloud platform, I noticed that the notaction augument for alicloud_ram_policy_document Data sources is not supported. This Data source is often used to define RAM policy. However, the notaction argument can be added in AliCloud Web Interface.

Therefore, I have raised this issue to inquire about the possibility of adding this notaction argument in alicloud_ram_policy_document Data source.

Category

AliCloud

Aspect

RAM(policy)

Details

notaction argument are not supported in alicloud_ram_policy_document Data sources.
image
image

Terraform Version

1.5.7

Affected Resource(s)

ram

Terraform Configuration Files

data "alicloud_ram_policy_document" "AliyunPowerUserAccess" {
  version = "1"
  statement {
    effect = "Allow"
    notaction = [
      "ram:*",
      "ims:*",
      "cloudsso:*"
    ]
    resource = ["*"]
  }
  statement {
    effect = "Allow"
    action = [
      "ram:ListRoles",
      "ram:CreateServiceLinkedRole",
      "ram:DeleteServiceLinkedRole"
    ]
    resource = ["*"]
  }
}

Debug Output

N/A

Panic Output

N/A

Expected Behavior

The notaction argument should be supported in alicloud_ram_policy_document Data source.

Actual Behavior

Not supported at present.

Steps to Reproduce

N/A

References

[alicloud_ram_policy_document]
(https://registry.terraform.io/providers/aliyun/alicloud/latest/docs/data-sources/ram_policy_document)

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

No branches or pull requests

1 participant