I am using the new support for EFS. Another stack outputs the ARN of the EFS and I use it as follows

functions:
  myLambda:
    handler: src/main.something
    fileSystemConfig:
      localMountPath: /mnt/efs
      arn:
        'Fn::ImportValue': ${self:custom.stage}-my-efs-access-point-arn

While this works, it throws the following warning during deploy:

Serverless:

Hi,

I wanted to enable binary support on API gateway, but could not find the way to do it via component's inputs.

Is this something that you would consider adding in the future?

If so, I can try to add this feature. It doesn't look too complicated.

Thanks!

It looks like the list with extensions on the website is incomplete. Just deployed a microservice running bref using ext-gd even though there is no mention of it here: https://bref.sh/docs/environment/php.html#extensions-installed-and-enabled

Describe the bug

I believe this is a bug, but I might just be missing how to properly use the containerize functionality.

The Dockerfile generated by https://github.com/bentoml/BentoML/blob/master/bentoml/clipper/__init__.py#L97 includes two args for PIP repos. However, the containerize functionality doesn't seem to expose these arguments. The problem is that this will override other p

Current behavior:
All the SQL activities either don't support Insert or are specific to a usecase

Expected behavior:
to be able to insert to a sql database in an activity

What is the motivation / use case for changing the behavior?
many workflows/pipelines require logging to a database

Additional information you deem important (e.g. I need this tomorrow):

fx access HTTP endpoint of docker engine to do image build and container run, but currently fx make docker endpoint to support HTTP with "socat" with docker run https://github.com/metrue/fx/blob/master/provisioner/darwin/darwin.go#L18, it'd would be great to migrate it to Go.

Describe the bug
JSON data files for SSG pages (e.g. `_next/data/{build id}/file.json) are not being cached by Cloudfront, meaning that subsequent calls always go to the origin (and trigger the Lambdas@Edge).

To Reproduce

1. Deploy a website with at least one SSG page.
2. Visit the SSG page once. This should cache the JSON data.
3. Refresh that page and observe the x-cache respons