eggressive commented 3 months ago

Description

Adding an argument (or a separate resource?) to aws_emr_studio resource would be great.

Currently, the provider lacks the necessary functionality to manage AWS EMR Studio workspaces. This is evident in a specific use case where the creation of an EMR EC2 cluster and EMR Studio is successful. However, when a customer creates a workspace and then destroys it, an unresolved dependency issue arises, leading to a failed run. This necessitates the customer manually deleting the Studio workspace, which is inconvenient. I'd like to avoid using “local-exec” in the above case.

Affected Resource(s) and/or Data Source(s)

aws_emr_studio

Potential Terraform Configuration

No response

References

https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/emr_studio

Would you like to implement a fix?

None

github-actions[bot] commented 3 months ago

Community Note

Voting for Prioritization

Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
Please see our prioritization guide for information on how we prioritize.
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.

Volunteering to Work on This Issue

If you are interested in working on this issue, please leave a comment.
If this would be your first contribution, please review the contribution guide.

eggressive commented 1 month ago

As it stands, AWS does not yet provide API for managing workspaces in EMR Studio: https://docs.aws.amazon.com/emr/latest/APIReference/API_Operations.html

Unless the option is available in the API it cannot be added to the AWS terraform provider. The very outdated thread in AWS forums doesn't bring any hope either: Programatically detach EMR clusters from EMR Studio workspaces

hashicorp / terraform-provider-aws