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

Documentation incorrect for the aws_workspace_directory #25628

Closed
csol01 opened this issue Jul 21, 2020 · 2 comments
Closed

Documentation incorrect for the aws_workspace_directory #25628

csol01 opened this issue Jul 21, 2020 · 2 comments

Comments

@csol01
Copy link

csol01 commented Jul 21, 2020

Hi There,

Apologies if this isn't the place to raise documentation issues, please point me in the right direction if I need to re-raise this elsewhere.

I've just been deploying out the aws_workspace_directory resource to register with a pre-existing directory service whereby only 1 of the directory service subnets is within an AZ that supports Workspaces. This isn't an issue as you can specify the subnets to use within the resource itself, and they don't need to be the subnets in which the directory service exists i.e.

resource "aws_workspaces_directory" "ms_ds" { directory_id = "<directory_id>" subnet_ids = [ "<subnet_id#1>", "<subnet_id#2>" ] }
However the documentation for this resource states that the subnet_ids value should be:

"(Optional) The identifiers of the subnets where the directory resides."

which is incorrect as it can be any subnets you want providing the workspaces facility is supported in those zones.

Chris.

@ghost
Copy link

ghost commented Jul 21, 2020

This issue has been automatically migrated to hashicorp/terraform-provider-aws#14276 because it looks like an issue with that provider. If you believe this is not an issue with the provider, please reply to hashicorp/terraform-provider-aws#14276.

@ghost
Copy link

ghost commented Aug 21, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Aug 21, 2020
This issue was closed.
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

2 participants