Jarred Ward
Jarred Ward
Code in question for `Sub` here: https://github.com/awslabs/goformation/blob/master/cloudformation/intrinsics.go#L113 The following minimal repro: ```golang cloudformation.Sub(`{"foo":"bar"}`) ``` Will remain as base64 in the template JSON output. Should be as easy as adding a...
The current JSON generation method uses `json.MarshalIndent` and generates a fair amount of cosmetic whitespace that bloats JSON file size unnecessarily.
We were getting stabilization errors on an `AWS::CloudFormation::ResourceVersion` of ours. The `schema.json` passed validation and generated correctly via `cfn-cli`. Anyway, here is the diff of the change to our `schema.json`...
The POM for DynamoDB local `com.amazonaws:DynamoDBLocal:1.11.477` in `https://s3-us-west-2.amazonaws.com/dynamodb-local/release` includes some binary dependencies: ```xml com.almworks.sqlite4java libsqlite4java-linux-amd64 ${sqlite4java.version} so runtime com.almworks.sqlite4java sqlite4java-win32-x64 ${sqlite4java.version} dll runtime com.almworks.sqlite4java sqlite4java-win32-x86 ${sqlite4java.version} dll runtime com.almworks.sqlite4java libsqlite4java-osx...
**What I'd like:** I'd to be able to configure the ECS agent to `ECS_AWSVPC_BLOCK_IMDS=true`.
### What version of rules_go are you using? `0.38.1` ### What version of gazelle are you using? `0.26.0` ### What version of Bazel are you using? `6.0.0` ### Does this...
### Is there an existing issue for this? - [X] I have searched the existing issues ### Current Behavior ### Expected Behavior I'd expect this query to not have linter...
The new `AWS::CloudFormation::ResourceVersion` & `AWS::CloudFormation::ResourceDefaultVersion` are currently [not supported](https://docs.aws.amazon.com/serverlessrepo/latest/devguide/list-supported-resources.html) in AWS SAR. Really bummed to have hit this. Is there any way you all could work w/ the SAR team...
Seeing internal failure errors when updating tags on `AWS::CloudFormation::ResourceVersion` resources. ### Repro Define a resource version similar to the following in a CloudFormation stack. As you can see, there are...
### What happened? The following mutation: ```graphql mutation { evaluate( expressions: { date: "1" } ) evaluate( expressions: { date: "2" } ) } ``` Executes first mutation field only...