Closed alexmensch closed 1 year ago
I'd put some caution at bumping to v1.x.y
as that implies you're moving out of the development phase and into stable version changes, assuming you're trying to follow semver. I think here you'd just bump x
in v0.x.y
. See https://semver.org/#spec-item-4
FYI @tjstansell I'm going to close out a number of issues around assignments and replace them with a single issue and a single new resource we're going to use for assignments.
Instead of the changes proposed in #65, we are going to introduce a new type of assignment resource. This change will be introduced in the v0.y.z major version, and we'll introduce an equivalent change for resources<>group assignments in a new v1.y.z major version.
--
Create a new
twingate_users_group_assign
resourceNew functionality
Arguments
user_ids
of typeset(string)
id
s obtained from thetwingate_user
ortwingate_users
data sources.group_id
of typestring
id
obtained from thetwingate_group
ortwingate_groups
data sources.Notes
groupUpdate(userIds[])
mutation in the provider so that any existing relationships are replaced with exactly what is set in this resource.Example usage
Create a new
twingate_users_group_add
resourceNew functionality
Arguments
user_ids
of typeset(string)
id
s obtained from thetwingate_user
ortwingate_users
data sources.group_id
of typestring
id
obtained from thetwingate_group
ortwingate_groups
data sources.Notes
twingate_users_group_assign
, this resource must instead use thegroupUpdate(addedUserIds[])
mutation to avoid changing any existing group assignments.Example usage