Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

New or Affected Resource(s)

• steampipecloud_XXXXX

Potential Terraform Configuration

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key.

References

• #0000

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

We need a data source for steampipecloud_organization_members. We have a multi repository setup with our terraform states being spread across separate repositories for separate teams and consequently these teams would have their own workspaces in steampipe cloud as well. There can be users who belong to more than one team. In case of a multi repository setup, end users of the steampipe terraform module would have no way of knowing whether a user is already a part of the steampipe cloud organization before adding them in as members.

Since a terraform apply would fail when trying to add an existing user (who has already been added as a part of the org from a different repository), we would need the ability to be able to list the organization members from a data source and filter existing users out in order to overcome this limitation.

I'm happy to help implement this in the provider unless this is already in the works as I see an API available in the SDK.

New or Affected Resource(s)

New data source:

• steampipecloud_organization_members

Potential Terraform Configuration

data steampipecloud_organization_members {
     organization_id = "o_abcdefghijk"
}

data steampipecloud_organization_members {
     handle = "org123-blah"
}

References

Getting following error while trying to create a workspace connection resource

Error: unexpected format of ID ("bose/aws_role"), expected <workspace-handle>:<connection-handle>

  with steampipecloud_workspace_connection.workspace_connection_org,
  on aws_role_connection.tf line 90, in resource "steampipecloud_workspace_connection" "workspace_connection_org":
  90: resource "steampipecloud_workspace_connection" "workspace_connection_org" {

Seems like the error is due to inconsistent ID in create and read operation
Create operation returning the ID in the below format
https://github.com/turbot/terraform-provider-steampipecloud/blob/main/steampipecloud/resource_steampipecloud_workspace_connection.go#L167
while the read operation is expecting below
https://github.com/turbot/terraform-provider-steampipecloud/blob/main/steampipecloud/resource_steampipecloud_workspace_connection.go#L206