prismacloud_policy redlock-auth requirement (400 err)

[0x53c]

Describe the bug

prismacloud_policy resource requires a redlock-auth token, while other resources do not.

Expected behavior

Terraform apply should succeed successfully without needing a unique auth workflow for the policy resource or documentation for setting up with this unique resource.

Current behavior

Many/Most of the other terraform resources are applied successfully; it is only when the prismacloud_policy resource is implemented that the redlock-auth 400 error occurs.

Possible Solution

Alteration of the policy endpoint may need to be adjusted to match the other endpoints. There is a mismatch somewhere.

Steps to reproduce

1. Write some terraform that includes prismacloud_policy resource
2. terraform apply
3. redlock-auth 400 error

Screenshots

Provider

Web Token Generation

Resource Declaration

ERROR

Context

This has halted my ability to create/manage custom policies via CICD+Terraform pipelines.
While not a complete blocker for other objectives that do not throw the same 400 error, there needs to be consistency across all terraform resources for the CRUD of resources or a documentation method to avoidance of this error

Your Environment

• Version used:
  We are leveraging Gitlab Managed Terraform State with TF version 1.3.6.

[welcome-to-palo-alto-networks]

🎉 Thanks for opening your first issue here! Welcome to the community!