Brandon Konkle

I thought taking your vitamins was a waste of time? ;-)

I'm running into this same limitation. I want my workers to be able to access services like ECS, KMS, Lambda, etc. To work around this, I'm using Terraform: * aws_iam_role...

My security group appears to have some arbitrary IP values:  My team works from home, so there's no way to guarantee the IP ranges they'll be...

Also - if I change this manually, will it be overwritten by `control-tower`'s next Terraform run?

I see now in the docs, "The control plane will be restricted to the IP control-tower deploy was run from." - how do we override this effectively in a dynamic-IP...

I think we may need to continue to defer this issue. The Chrome bug hasn’t been fixed yet, and it doesn’t appear to be firing the `wheel` event at all...

This is impacting my team because of this issue with Cypress on Docker: https://github.com/cypress-io/cypress/issues/350 We need to be able to set ipc to `host` to prevent renderer crashes.

I ended up ditching aliases altogether, and going with `lerna` and a monorepo structure. :-)

Demo project here, with both sides of the interaction: https://github.com/ecliptic/reason-events

@mhallin It's the `id`, `createdAt`, and `updatedAt` fields - fields that are automatically set by Postgres and don't need to be provided initially.