we do not expose a create endpoint for account_memberships -- these are handled upon creation of the actors themselves (bots / users)
However, we could still create a Terraform resource, but this would require that practitioners always import the resource via terraform import prefect_account_membership
Another way to handle this could be that upon Create of the resource, we query for account_memberships based on the email attribute, and then hit the PATCH endpoint with the fetched membership ID. Update wouldn't be a problem, as we could just use the membership ID in state
This issue will be deprioritized for the initial provider launch
Note:
account_memberships-- these are handled upon creation of the actors themselves (bots / users)terraform import prefect_account_membershipCreateof the resource, we query foraccount_membershipsbased on theemailattribute, and then hit the PATCH endpoint with the fetched membership ID.Updatewouldn't be a problem, as we could just use the membership ID in stateThis issue will be deprioritized for the initial provider launch