lambda

Is your feature request related to a problem? Please describe.
Currently, there are two ways to create HTTPTrigger using the fission command.

1. fission fn create with below parameters

  --url=''                              URL pattern (See gorilla/mux supported patterns)
  --prefix=''                           Prefix with which functions are exposed. NOTE: Prefix takes
    

this will very quickly get out of hand if we allow it, i realize we don't have principles written down anywhere but to date one of them has been that binaries 'just work' without having to do any configuration. currently a user must set FN_MAX_REQUEST_SIZE, FN_MAX_RESPONSE_SIZE -- neither of these should be required to run.

test case:

cd tests/fn-system-tests/
go test -v

this

This is

• Bug

Expected Behavior

When a page is created in Page Builder, the list of pages should correctly show the Created by label, showing the author of the page.

Actual Behavior

The label says N/A.

The API call however, returns the data correctly:
![image]

If basePath is set in next.config.js, the build would put static assets within ${sererlessBuildOutDir}/assets/${basePath}.

However, in the CDK construct (NextJSLambdaEdge), it tries to read the assets from ${sererlessBuildOutDir}/assets without including the basePath

https://github.com/serverless-nextjs/serverless-next.js/blob/145c16d9e163aca7b5f6a753f60404363c842b8f/packages/ser

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!

When creating an AWS Lambda function with a custom IAM Policy cloudformation seems to fail to create/update the function.
In my case I have the following policy added the following:

class MyController < ApplicationController
  iam_policy(
      version: "2012-10-17",
      statement: [{
                      action: ["s3:GetObject",
        

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):