A ZSH theme optimized for people who use:
- Solarized
- Git
- Unicode-compatible fonts and terminals (I use iTerm2 + Menlo)
For Mac users, I highly recommend iTerm 2 + Solarized Dark
uninstall
JetBrains settings:curl -sL https://gist.github.com/denji/9731967/raw/jetbrains-uninstall.sh | bash -s
backup
JetBrains settings:curl -sL https://gist.github.com/denji/9731967/raw/jetbrains-backup.sh | bash -s
// Promise.all is good for executing many promises at once | |
Promise.all([ | |
promise1, | |
promise2 | |
]); | |
// Promise.resolve is good for wrapping synchronous code | |
Promise.resolve().then(function () { | |
if (somethingIsNotRight()) { | |
throw new Error("I will be rejected asynchronously!"); |
a4b.amazonaws.com | |
access-analyzer.amazonaws.com | |
account.amazonaws.com | |
acm-pca.amazonaws.com | |
acm.amazonaws.com | |
airflow-env.amazonaws.com | |
airflow.amazonaws.com | |
alexa-appkit.amazon.com | |
alexa-connectedhome.amazon.com | |
amazonmq.amazonaws.com |
/* | |
I was curious as to whether it was possible to make resources | |
created using CDK constructs work with raw CloudFormation | |
resources and vice versa. | |
This aws-cdk app demonstrates a VPC and an ELB that belongs to it | |
in different, dependant stacks, leveraging CFN outputs / imports, | |
and leveraging CDK's method of passing information from one | |
stack to another. | |
*/ |
import { aws_eks as eks } from "aws-cdk-lib"; | |
import { aws_iam as iam } from "aws-cdk-lib"; | |
import { aws_ec2 as ec2 } from "aws-cdk-lib"; | |
import { aws_ssm as ssm } from "aws-cdk-lib"; | |
import { Construct } from "constructs"; | |
import { Duration, CfnJson } from "aws-cdk-lib"; | |
interface KarpenterProps { | |
/** | |
* The FargateCluster on which karpenter needs to be added |