Tom Denley

I'm looking to deploy a new concourse setup, and I was hoping to use m5 instances for the workers. Is there an update on this issue? Would it be possible...

As much as I applaud your good work, this change-set is rather large, and hence difficult to digest. Also, there appears to be a number of unrelated changes mixed in...

Hey Sandro, I'm kinda looking at pull requests, although I'm concentrating on getting a release out before taking much new code in.

I note that there is an official docker image for the AWS CLI now (see https://github.com/aws/aws-cli/issues/3553#issuecomment-606952933), does this set a precedent that might see an official cfn-lint image?

FYI, some [relevant discussion on Clojurian's Slack](https://clojurians.slack.com/archives/C073DKH9P/p1704898858380729). The conclusion was that one should probably opt for [re-frame-fetch-fx](https://github.com/superstructor/re-frame-fetch-fx) over re-frame-http-fx these days.

For reference, the https://github.com/concourse/docker-image-resource takes aws_access_key_id/aws_secret_access_key params and can push/pull from ECR

Looking at the instructions for deploying to CF from Google Container Registry (GCR) https://docs.cloudfoundry.org/devguide/deploy-apps/push-docker.html I think the same issue applies.

This is also breaking our build too. Same error, but on chart.js ``` Node(COMPUTED_PROP): node_modules/chart_DOT_js/dist/chart.cjs:509:16 const { [iAxis]: index , [vAxis]: value } = item; Parent(OBJECT_PATTERN): node_modules/chart_DOT_js/dist/chart.cjs:509:14 const { [iAxis]:...

The new version seems to work perfectly for us, thanks

@SaphMB are you the maintainer of control-tower now? Any chance you could advise on this one please.