You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not going to let any program access AWS with keys that can do lots of things. Maybe there is a way to create proper IAM role with only necessary policies to allow stack creation, but I don't know how that would work.
But good way allow stack creation manually would be to add option (or modify --dry-run) to print the CloudFormation JSON or Yaml template. User can then check the template is fine and create the stack from AWS Console.
I'm not going to let any program access AWS with keys that can do lots of things. Maybe there is a way to create proper IAM role with only necessary policies to allow stack creation, but I don't know how that would work.
But good way allow stack creation manually would be to add option (or modify
--dry-run
) to print the CloudFormation JSON or Yaml template. User can then check the template is fine and create the stack from AWS Console.Instead of pprint here, https://github.com/confetti-clj/confetti/blob/master/src/confetti/boot_confetti.clj#L193 this could call cheshire/generate-string or similar (with key-fn that converts snake-case to CamelCase). Amazonica probably already has a function to translate clj data to JSON.
The text was updated successfully, but these errors were encountered: