RB
nice idea. FYI 2fa is handled by twofactorauth and dongleauth projects
Instead of creating a new module, it would probably be better to reuse an existing one that supports overriding the ami. See https://github.com/cloudposse/terraform-aws-dynamic-subnets#input_nat_instance_ami_id And a complete example https://github.com/cloudposse/terraform-aws-dynamic-subnets/blob/master/examples/complete/main.tf
@ktully Why is your fork `DontMessWithPaste` instead of `DontFuckWithPaste` ? :disappointed: that you removed the emotional expletive that increases our satisfaction to use this addon
I appreciate all the time you put into these examples. As for example 2, we currently ignore each individual using the `owner_checker_ignored_owners` input. I'd prefer not to ignore each owner...
It's definitely missing some permission because it works for our admin user just not the least privilege user with the perms from the README
@mkuzmin saw you put the perms in the readme 10 months ago. Is there another perm? I'm on vsphere esxi 6.7
Looks like two things should be implemented for metadata. * custom attributes which are called custom fields in the [govmomi package](https://github.com/vmware/govmomi/blob/master/object/custom_fields_manager.go) * tags https://github.com/vmware/govmomi/blob/master/govc/tags/create.go#L75 Does look fairly simple to implement!...
As useful as this is, I'm wondering if a cloudtrail specific policy is too specific for this module. All the other toggles are generic enough to work for many use-cases...
/test all