Add support for adding tags to r/vra_project

[pgsmith123]

vRA version
8.4.1
Terraform version
1.0.1
terraform-provider-vra plugin version
0.3.8

Is your feature request related to a problem? Please describe.
When creating a project we would like to utilize resource tags.

Describe the solution you'd like
I would like to be able to add resource tags to a project via the vra_project terraform resource.

Describe alternatives you've considered
Manually adding the tags after deployment

Additional context
none

[lolichet]

HI,

Any plan in the roadmap for this ?

Thanks.

[frodenas]

We are currently working on switching to the new Project Service APIs (instead of using the IasS Project APIs). When the switch is done, then we will be able to implement this feature.

[lapawa]

Any progress on this issue? I'm migrating Business Groups from vRA7 to vRA8 Projects. And I have to change some Custom Properties to Tags...

[frodenas]

@lapawa it's on our backlog, but unfortunately I cannot provide an estimation on when we can deliver this.

[AndreaTosti]

Is there any news on this? is the implementation planned also for vra_deployment resources?

[cathode911]

Any updates? Currently we have to manually set the tags per each project which can be really time consuming and open vast area for human error

[Arderos]

+1. Would be of an extreme use for us.

[ykezlya]

Very useful thing, look forward to the implementation!

[cathode911]

@frodenas Do you have an estimation by any chance? From what I see, the development of this provider is pretty much dead, although sales/presales had a pitch that new shiny terraform provider will cover all our needs and even more

[pgsmith123]

Bumping, any updates on this functionality?

[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!

[cathode911]

bumping

[pgsmith123]

bump, still looking for this functionality nearly 4 years later...

[tenthirtyam]

This is still dependent on the upstream SDK transitioning to the Project Service APIs instead of the IaaS Project APIs (example).

Most of the services have transitioned to the OpenAPI Specification 3 v8.11, but the current tooling (go-swagger) used generate the SDK from the swagger specs only supports OAS2.

Supporting the newer versions will involve switching to a new generator that supports both OpenAPI spec versions, affecting this provider.

A similar effort was done for terraform-provider-vcf and its vcf-go-sdk with oapi-codegen last year, but for provider and it's supporting SDK this needs to be prioritized by the VCF Automation product team.

Ryan Johnson
Distinguished Engineer, VMware by Broadcom