aws-lambda

Is there an existing issue for this?

• I have searched existing issues, it hasn't been reported yet

Use case description

Currently, we have websocket-related properties configured directly on provider level:

• provider.websocketsApiName
• provider.websocketsApiRouteSelectionExpression
• provider.websocketsDescription

This is not consistent with how iam, httpApi or

Version

5.29.0

Operating System

/

Browser

/

What steps will reproduce the bug?

Just try issuing the following mutation, and you should be able to see the error message on the right:

What is the expected behavior?

We

Issue Summary

Building with serverless results in an error:

Build error occurred
TypeError: Class extends value undefined is not a

Is this feature request related to a new or existing Amplify category?

New category

Is this related to another service?

No response

Describe the feature you'd like to request

Support a path argument on amplify plugin add to simplify command:

amplify plugin add --path $(pnpm root -g)/amplify-graphql-seed-plugin

Currently we need to first capture the absolute path, and

If we override PHP_INI_SCAN_DIR then the "special php.ini" files will not be used.
Ie: https://github.com/brefphp/bref/blob/0.5.9/runtime/layers/fpm/php.ini

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!

#16398 introduces a validate mode for caches which uses ShardedLmdb::exists (rather than load_bytes_with) for the first time. But because it is always consumed in a batch mode (to check that all files referenced by a cache entry exist), that method should likely be converted into a batch call which [partitions by shard similar to store_bytes_batch](https://github.com/pantsbuild/pants/blo

Current behavior (how does the issue manifest):
The lambda invoke activity returns a value object which includes the payload and the []byte serialized response. This really has no real purpose and causes confusion between the unmarshaled payload in the return param result .

Expected behavior:
Remove the value param, as both the unmarshaled payload and the status are both returne

Right now settings are just passed in through the settings file. This is somewhat limiting if there is a value that will be dynamic with deployments (such as a docker image file, etc.) We should support accepting settings through environment variables, the CLI, the current settings file, and any mix of those.

The order of precedence with mixed should be CLI -> environment -> config file.

If

https://github.com/metrue/fx/runs/2779702719?check_suite_focus=true