Existing user assignment at importing groups

[stef-73]

Hi all,
I'm about to import some existing groups from SCI for getting them under terraform control (to be more precise: opentofu). The import is straight forward, but as I don't have and not want to have the users in the terraform repo, the resources created will either delete existing user assignment or I risk getting a drift by adding users to groups outside terraform. I'm not sure if the current design of the group attributes with the assignment to users is the right way? Maybe it's a better approach to separate user assignment from the group data? Something similar is done in the BTP provider with the role_collection resource and the role_collection_assignment resource separated.
I've found a workaround by using data source sci_group, but this is a little bit weird.
KInd regards,
Stefan

[lechnerc77]

@vipinvkmenon @diya-dhan can you check this issue of @stef-73 ? As we are in beta a change of the schema is not a big issue if needed

[vipinvkmenon]

Hi @stef-73 ,

The current resource tries to match with the API behind it.
The Groups API in SCI is the same. Members are assigned as part of the Group during the creation/update of a Group.

In BTP, there are separate APIs that handle the creation of role_collection and the assignment of the same.
Hence the possibility of making separate resources.
Nonetheless, we'll have a discussion and see how to proceed.