Add support for managing policies and policy definitions

[an2ane]

Code of Conduct

This project has a Code of Conduct that all participants are expected to understand and follow:

• I have read and agree to the project's Code of Conduct

Description

vRA Version : SaaS (ATM 8.10.0)
Terraform : >= 0.13
vRA Provider : 0.5.3

With the "new" change in 8.8.2 with Content Sharing Policy, the scope went from organization to project. Now, to share day-1 workflows with all the projects, we have to create a Content Sharing for each project. Because the vra_provider allows to create projects through Terraform, it would be nice to also create any kind of policies (day-2, approval, content sharing, deployment limit, lease and resource quota) as well.

Describe alternatives you've considered

Currently, we have created a workflow we are launching through vra_deployment to create 2 content sharing policies. However, when we destroy the project in Terraform, it does not destroy those content sharing policies.

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

[japerrin]

Hi , it would be nice, to be able to have a "data" on "vRO worklows, currently it's only Cloud templates like this:

data "vra_blueprint_version" "this" {
blueprint_id = var.blueprint_id
id = var.blueprint_version_id
}

[Arderos]

+1

[tenthirtyam]

it would be nice, to be able to have a "data" on "vRO worklows, currently

Please open a separate enhancement issue as this is off-topic.

[github-actions]

Marking this issue as stale due to inactivity. This helps us focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context.
Thank you!