-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
aws_instance: set windows_password attr on windows instances #30
Comments
This comment was originally opened by @antonosmond as hashicorp/terraform#3148 (comment). It was migrated here as part of the provider split. The original comment is below. 👍 Thanks for raising this Paul it's exactly what we need! |
This comment was originally opened by @adamveld12 as hashicorp/terraform#3148 (comment). It was migrated here as part of the provider split. The original comment is below. What if you can provide the pem key file used to create the instance and terraform just deals with decrypting the password itself with the key? This works in principle similarly to how Packer works with Windows instances. (Packer generates a temp key file, creates the resource with it, and then gets the password for access from what I can tell). This would be consistent with how the SSH connection works (they both would be taking a private key in this case) so it seems like it would bring some nice consistency with how they both work. |
This comment was originally opened by @epsilon-jpage as hashicorp/terraform#3148 (comment). It was migrated here as part of the provider split. The original comment is below. This is also a blocker for me. I need to be able to perform remote execs on a windows server but want Terraform to query AWS for the Windows password and not need me to key it in or put it in a file. |
This comment was originally opened by @johnjelinek as hashicorp/terraform#3148 (comment). It was migrated here as part of the provider split. The original comment is below. 👍 |
This comment was originally opened by @deftflux as hashicorp/terraform#3148 (comment). It was migrated here as part of the provider split. The original comment is below. I started a pull request #5675 that implements this, since we need this function too. It works a little differently than described here, mainly to avoid the decrypted password from ending up in the terraform state file. This is my first time developing for terraform (and in Go for that matter), so I'd appreciate some feedback. |
This comment was originally opened by @mojowrkn as hashicorp/terraform#3148 (comment). It was migrated here as part of the provider split. The original comment is below. Also a blocker here, any updates? |
This comment was originally opened by @deftflux as hashicorp/terraform#3148 (comment). It was migrated here as part of the provider split. The original comment is below. Back when I implemented this feature, it worked for me. It may need to be merged with changes released since then. However, we no longer need to use terraform to provision windows instances in our particular use case, so I haven't done any more work on it. The pull request is only missing acceptance tests. At that point, it should meet their development guidelines. Someone with some experience writing acceptance tests for terraform would be able to do this much quicker than I could. Anyone? |
Any update on this? |
@smastrorocco Boom! One piece of the puzzle is ready: #2219 Show your support over there to get it merged. |
@deftflux Nice, I commented over there. Thanks! |
This has been released in version 1.12.0 of the AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. |
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! |
This issue was originally opened by @phinze as hashicorp/terraform#3148. It was migrated here as part of the provider split. The original body of the issue is below.
On
Read
for AWS instances, ifplatform
isWindows
, callGetPasswordData
and populate awindows_password
attribute with its contents.This should allow the
remote_exec
provisioner to be used on Windows instances like this:The text was updated successfully, but these errors were encountered: