Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for AWS Workspaces #10794

Closed
mootpt opened this issue Dec 16, 2016 · 8 comments
Closed

Support for AWS Workspaces #10794

mootpt opened this issue Dec 16, 2016 · 8 comments

Comments

@mootpt
Copy link
Contributor

mootpt commented Dec 16, 2016

Support for AWS Workspaces would be great, especially since there is existing support for AWS directory service directories in Terraform. Something like:

resource "aws_workspaces_workspace" {
  bundle_id              = "Some Bundle Id Here"
  directory_id           = "${aws_directory_service_directory.bar.id}"
  user_name              = "foo"
  root_volume_encryption = true,
  user_volume_encryption = false,
  volume_encryption_key  = "${aws_kms_key.foo.key_id}"
}

Ideally it would be nice to also have a aws_workspaces_bundle resource, but I'd settle for the former.

@liamjbennett
Copy link
Contributor

I have done most of the work for this here: #7806 however it was blocked due to a missing API allowing you to register your directory service for use with workspaces.

@bsft-it-git
Copy link

@liamjbennett, I noted some feature announcements that I thought might mean some of the gaps in the APIs have been filled:

https://aws.amazon.com/about-aws/whats-new/2017/02/amazon-workspaces-now-supports-interforest-trusts-in-aws-directory-service-for-microsoft-active-directory-enterprise-edition/

@liamjbennett
Copy link
Contributor

@bsft-it-git sadly not. I am keeping an eye on this issue very closely and I know the missing API is on the backlog for the workspaces team.

@cmaxwellau
Copy link

@liamjbennett

I work for AWS, and have a customer that would like to use terraform for workspaces.

Would one of you be able to concisely describe the issue for me so that I can pass it on to the service teams?
Cam

@liamjbennett
Copy link
Contributor

@cmaxwellau it’s a missing api for registration of the directory which prevents us writing tests for the terraform resources.

I raised this as a forum post in 2016 with reference to the internal api: https://forums.aws.amazon.com/thread.jspa?messageID=749994&#749994

As I understand it, this may actually be more the responsibility of the ADS team not the Workspaces team.

@pjohnstonv
Copy link

wot

@coderwearsprada
Copy link

Any updates on this topic?

@bflad
Copy link
Contributor

bflad commented Feb 11, 2019

Hi Folks 👋

Since Terraform 0.10, Terraform providers (e.g. AWS resources within Terraform) are no longer distributed as part of Terraform Core and have their own release cadence. For this issue in particular, it was migrated to hashicorp/terraform-provider-aws#434, but the comment from the GitHub bot is missing 😖. You can follow that issue for additional updates.

I am going to lock this issue as it is no longer applicable to this repository and has a migrated issue for tracking.

@hashicorp hashicorp locked and limited conversation to collaborators Feb 11, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

9 participants