[CBR] - Possibillity to assign only a new ECS(Server), Disk (EVS), SFS (3.0 for future) to an existing vault.

[uli-max]

Description of the enhancement

In the actual implementation i can only add/remove, ECS(Server), Disks( EVS), SFS (Turbo maybe not so interesting for this, but upcoming SFS 3.0), to the main object of the vault.

https://registry.terraform.io/providers/opentelekomcloud/opentelekomcloud/latest/docs/resources/cbr_vault_v3

But it ist not possible to do just an simple, "assignment, associate", which we offer for a lot of services only to ECS(Server), Disks( EVS) (and whatever CBR offer in future).

Having therefore an simple assingment / associate - provider task would be helpful.

Examples: (from network)
https://registry.terraform.io/providers/opentelekomcloud/opentelekomcloud/latest/docs/resources/vpc_bandwidth_associate_v2

(from IAM / assigement)
https://registry.terraform.io/providers/opentelekomcloud/opentelekomcloud/latest/docs/resources/identity_role_assignment_v3

From API persipective it should be possible.

https://docs.otc.t-systems.com/cloud-backup-recovery/api-ref/cbr_apis/vaults/associating_resources.html

[artem-lifshits]

Hello @uli-max could you describe a reasoning for this enhancement?
If we accept this then 2 new resources will have to be created (one for vault and another one for association) with same functionality that we already have and that wouldn't bring anything new to the table.
Moreover it might be unclear for customers which CBR vault resource should be used and why there are 2 similar resources with same API version.

Looking forward for your reply.

[uli-max]

Just to make adding/remove EVS/Server to/from a vault easier, without touching the complete code/definition of vault.
For the initial definition of a vault the actual way is ok, but if you add Disks/Servers you need need to know also to change the definition of vault. Having a way todo it similar like the provided samples makes it easier.