I have created a serverless project for python on AWS, which works fine... until I try to re-use the project directly after checkout. Any CLI command exits with the following error:

 sls help
 
 Serverless Error ---------------------------------------
 
  Serverless plugin "serverless-python-requirements" not found. Make sure it's installed and listed in the "plugins" section of your ser

Summary

Currently Kong supports writing configuration in a file, in YAML or JSON.
To provide a more flexible configuration, especially for those running Kong in different environments (dev, staging, production), an option to write configuration in lua can be very useful.

Additional Details

There are many use-cases that come to mind:

• Using environment variables inside the d

Feature Request

Is your feature request related to a problem? Please describe:

This is a really minor nit, but the EXPLAIN output on binary strings is different from what I expected:

CREATE TABLE t1 (
 id INT NOT NULL PRIMARY KEY auto_increment,
 b varchar(255) not null,
 c varbinary(255) not null,
 index (b),
 index (c)
);


INSERT INTO t1 (b,c) VALUES ('a', 'a'),('b

Move all Dockerfile samples to non-root user

Expected Behaviour

As an OpenFaaS end-user, I want to run all samples on my OpenFaaS cluster, even with the new non-root feature enabled.

Current Behaviour

Describe the bug
Any attempt to test a subscription directly to the Prisma server via Playground returns the following error:

The provided query doesn't include any known model name. Please check for the latest subscriptions API.

In review of the WS transactions in the browser console, I can see I am receiving this response from the Prisma endpoint, but nothing is being logged by Pri

The seccomp filters are tailored for the Firecracker musl build. We should specify how to run Firecracker when building it with gnu as well.

Requested by @rbrasga in firecracker-microvm/firecracker#1515 (comment)

The README at https://github.com/Miserlou/Zappa#custom-aws-iam-roles-and-policies-for-execution talks about using manage_roles: false to manually set a role for custom permissions.

This along with Miserlou/Zappa#244 led me down a rabbit hole.

However, if all you want to do is restrict the permissions of the Lambda itself, it seems that the partially documented `at

I made up a guide to setup Firebase services into a real-world scenario with cutting-edge technologies. I think you could get some insights on DX of your services and how they are used out in the wild (or add it to this examples repository).
Tech used: Quasar (Vue), TypeScript, Jest (unit testing), Firebase Firestore, Cloud Functions, RxFire.

Inside the guide there are some helpers and code ma

Along with the General Guides, it might be helpful to add a niche guide section, which is broken down by AWS service. Happy to issue a PR with some quality tutorials as an example.

If I were to deploy cube.js using AWS serverless architecture, is athena required?

The docs https://cube.dev/docs/deployment#serverless do not mention whether Athena is optional or required. But when reading it, I assume it is required because there are athena keys in the serverless.yml config. I'm evaluating the idea of using Postgres RDS as the sole datasource for cubejs.

Prerequisites

• I am running the latest version. (up upgrade)
• I searched to see if the issue already exists.
• I inspected the verbose debug output with the -v, --verbose flag.
• Are you an Up Pro subscriber?

Description

It would be great to add regex capabilities to redirects like so:

redirects: {
  "/folder/:slug(regexhere)": {
    "location": "https

I tried to install the dotnet example using:

install -u https://github.com/serverless/examples/tree/master/aws-dotnet-rest-api-with-dynamodb -n dotnet_example

but it responds with:

Serverless Error ---------------------------------------

serverless.yml not found in .../dotnet_example

So I think the "-n my-project" in the README is perhaps not what is actually needed he

Hello,
Thanks for the job you've done! Chalice is the very easy framework for newcomers and flask developers.

I've been learning the framework only for 2 weeks and regularly getting errors related with aws policies. The official content about the policies is minimal. And auto-policy can't do this job by the right way if you want to add more than just a 'hello world' function.

Run **chalice

Current behavior

Issue: Windows + minikube + MinGW + GitBash + make (gets stuck)

asouza@ASOUZA-DESKTOP MINGW64 /c/Code/dapr/dapr (master)
$ make test-e2e-all
DAPR_TEST_NAMESPACE=dapr-tests DAPR_TEST_TAG=dev DAPR_TEST_REGISTRY=docker.io/artursouza DAPR_TEST_MINIKUBE_IP= go test -v -tags=e2e ./tests/e2e/...

Workaround: see how I had to manually run the same command but set t

Running Pulumi CLI commands in CI is failing with the following error:

error: could not get cloud url: unmarshalling credentials file: unexpected end of JSON input

The following scripts are representative of what was running when the error happened:

# prepare.sh

curl https://sdk.cloud.google.com | bash > /dev/null
export PATH=$PATH:/root/google-cloud-sdk/bin
KEY_FI

https://github.com/kubeless/kubeless/blob/master/docs/runtimes.md

These default container images can be configured via Kubernetes environment variables on the Kubeless controller's deployment container. Or modifying the kubeless-config ConfigMap that is deployed along with the Kubeless controller. For more information about how to modify the Kubeless configuration check this guide.

Apar

Writing a function takes a lot of steps. In the case of a Java function, a Maven project needs to be created and the dependencies need to be added. For other languages, there is a simular experience.

After writing the function, specs need to be generated. These include a Package, Function and a trigger. Names need to match in multiple places, so a lot could go wrong. Below is a basic example fo

Hi,

It would great if there was documentation on the steps taken by sam build. My concrete use case is that I'd like to know how it finds and installs packages for Python Lambda functions so I can figure out the best way to structure my project. More specifically, does it just do a pip install -r and copies the source files or does it build my package with setuptools?

Thanks!

(Edit

The typescript runtime was recently added to openwhisk but we do not yet have docs for the runtime and it is missing from runtimes.json.

We need a doc like https://github.com/apache/incubator-openwhisk/blob/master/docs/actions-nodejs.md for typescript functions.

Adding the runtime to the runtime manifest can be done per https://github.com/apache/openwhisk/blob/master/docs/actions-new.md#the-

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

https://emotion.sh/

After this change in Material UI: mui-org/material-ui#6115

I see various references to bom in the build file, docs, etc. E.g. the docs say "The no longer used group for Graal is no longer part of the bom". I'm not sure what this means. It would be useful to add a definition for bom (I'm guessing it's not the definition I know of "byte order mark" 😉)

• Main website searches through sourcecode OR public services
• Dashboard searches through your services
• Docs search through docs

More importantly, almost all widgets look the same.

I think we need consistency here: either give all widgets the same functionality (dropdown for public services, sourcecode, your services, and docs) or change how they look. I think first option is ideal.

Currently, logging routes just uses console.log. Gets pretty annoying when you're trying to suppress serverless. (i.e. serverless.cli = { log: () => {} }

https://github.com/dherault/serverless-offline/blob/59ff77f18745c11d527aaff78220b6c9b36a7249/src/serverlessLog.js#L60-L70

we want to use swagger integrated with API document under aws-serverless-express framework, so any document/guideline to follow?
if we follow some code rule to define the API method then generate the API document and show in swagger it is perfect