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

Directory Service Shared Directory Support (Share Directory Accepter Resource) #6005

Closed
bflad opened this issue Sep 27, 2018 · 2 comments · Fixed by #24766
Closed

Directory Service Shared Directory Support (Share Directory Accepter Resource) #6005

bflad opened this issue Sep 27, 2018 · 2 comments · Fixed by #24766
Labels
new-resource Introduces a new resource. stale Old or inactive issues managed by automation, if no further action taken these will get closed.
Milestone

Comments

@bflad
Copy link
Contributor

bflad commented Sep 27, 2018

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 "me too" comments, 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

AWS recently announced support for cross-account shared Microsoft Active Directory resources: https://aws.amazon.com/about-aws/whats-new/2018/09/aws-directory-service-share-directory-across-accounts-and-vpcs/

To properly support this setup, it looks like we'll need to implement the following:

New or Affected Resource(s)

  • aws_directory_service_directory_share_accepter

Potential Terraform Configuration

# Example implementation, details may change during development
resource "aws_directory_service_directory_share_accepter" "example" {
  shared_directory_id = "${aws_directory_service_directory_share.example.shared_directory_id}"
}

References

@github-actions
Copy link

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

@github-actions github-actions bot added the stale Old or inactive issues managed by automation, if no further action taken these will get closed. label Sep 16, 2020
@ghost
Copy link

ghost commented Nov 17, 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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

@ghost ghost locked as resolved and limited conversation to collaborators Nov 17, 2020
@github-actions github-actions bot added this to the v4.22.0 milestone Jul 2, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
new-resource Introduces a new resource. stale Old or inactive issues managed by automation, if no further action taken these will get closed.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant