Clojurians Log v2

advice specific to redshift or in general? In general the only way something can traverse something fast is if it's close together. As in, you have to store things in the sorted order. In database speak, that's indexing. space for time.

https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/intrinsic-function-reference-ref.html

probably !REF https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/intrinsic-function-reference-ref.html

lol. thanks @jjttjj

i'll figure it out from here i'm sure, but this example is funny because it has a ref but not the important bit where it shows the other end of the edge.

MyEIP:
  Type: "AWS::EC2::EIP"
  Properties:
    InstanceId: !Ref MyEC2Instance # <--- where is this declared?

Depending on the resource type, it may or may not return what you need for the other resource parameter. Sometimes you'll need to use Fn::GetAtt instead. I find i consult this a lot https://theburningmonk.com/cloudformation-ref-and-getatt-cheatsheet/

The Ref argument refers to either the name you give the resource (ie, names on the level of MyEIP in that example, MyEC2Instance would be a sibling ), or the name of a parameter of your template. (and maybe some more stuff I'm forgetting)

This is how cloudformation makes me feel on the inside.

Haha yup it definitely feels like coding in json a bit, wait til you get to if statements/conditionals

I've been on an ongoing deep dive in to cloudformation. Overall I like it, after getting comfortable with the ways to do things. In the end I like that it's just JSON and it's nice that you can just stick some edn in a clojure file and break it up and add as many helpers as you want before calling some json library to write it out as json.

I'm certainly glad it's an option! I wonder if there are any clojure wrappers that do some really fun runtime analysis to try and help you intelligent build and update cloudformation though. You could pull the api and return suggestions in the editor. etc... I know you can output CF from the design tool, but it doesn't seem to actually help you with anything other then putting pictures together. which is odd... Is "taskdefination" the name of the instance of this task below?

taskdefinition: 
  Type: AWS::ECS::TaskDefinition

yes

{:Resources {"<your names>" {:Type "" :Properties {...}} ...}

There are a few attempts at tooling in clojure ie https://github.com/brabster/crucible, but I don' think it has that many resource types supported and isn't actively being updated

the specification for everything is here though so it shouldn't be too hard to get an auto-complete thing going https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cfn-resource-specification.html

interesting, ill have to take a look. If for no other reason then it will probably help me conceptualize whats going on.