mconigliaro

We're seeing this with https://registry.terraform.io/modules/terraform-aws-modules/eks/aws/ since yesterday afternoon. ``` module "eks" { source = "terraform-aws-modules/eks/aws" version = "18.24.1" ... } ```

Make an option like `fips: true` and then only use FIPS endpoints (see the URL in my original post) when communicating with AWS. Super easy.

It seems to not like the space between `|obj|` and `puts`.

Same problem here. ``` ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-darwin11.3.0] ``` ``` #!/usr/bin/env ruby require 'net/dav' require 'tmpdir' uri = "http://localhost:30080/cargohold/" dav = Net::DAV.new(uri) dav.verify_server = false dav.credentials("airspace", "carousel") cargo...

For what it's worth, I believe the error message from Net::HTTP is erroneous. Using netcat (`nc -l 30080`), I can see that the Content-Length header is in fact being sent...

OK guys, this definitely has something to do with authentication. Notice that in my last comment, no Authorization header gets sent with the request. I also get 401 (Unauthorized) errors...

In case anyone needs to import the existing access entry: ```bash $ terraform import 'module.cluster_name.module.eks.aws_eks_access_entry.this["cluster_creator"]' cluster_name:principal_arn $ terraform import 'module.cluster_name.module.eks.aws_eks_access_policy_association.this["cluster_creator_admin"]' cluster_name#principal_arn#policy_arn ```

This is what worked for me: ```yaml provider_raw_config_args: - "customize ['createmedium', 'disk', '--filename', 'example', '--size', '2048']" - "customize ['storageattach', :id, '--storagectl', 'SCSI', '--port', '2', '--type', 'hdd', '--medium', 'example.vdi']" ```

I think I was having this same problem, but setting `create_attachment = false` in the target group resolved it for me.

Even better would be a generic SQL backend using something like sqlalchemy so we can pick whichever SQL backend we want. I think this has come up before. I'd be...