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

Context

When deploying a Django app (over 50mb) from a Windows 10 machine the tarball retains the Windows directory separators '\\', when deployed to Lambda this causes the error "No module named 'django.core.wsgi': ModuleNotFoundError"

Expected Behavior

1. tarball should keep Unix directory separators

Actual

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.

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

Description:

I have created a stack with an AWS::Serverless::Function and an AWS::Serverless::Api resource with the intention of restricting access to an IP address range. An example stack looks as follows:

{
  "AWSTemplateFormatVersion": "2010-09-09",
  "Transform": "AWS::Serverless-2016-10-31",
  "Globals": {
    "Function": {
      "Timeout": 10,
      "MemorySize":

Hi

I got module not found error when deploying, I specify the function to use layers
{ "version": "2.0", "app_name": "myapp", "stages": { "dev": { "api_gateway_stage": "api", "manage_iam_role": false, "iam_role_arn": "arn", "lambda_functions": { "myfunc": { "layers": ["layer1", "layer2"] } } } }, }

I di

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

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

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

Is your feature request related to a problem? Please describe.
Can you please add the screenshot and precise step-by-steps to documentation to deploy cloud custodian in both AWS, Azure and GCP. Can you also provide the same kind of enhanced screenshot version for installation / working of tools like c7n-mailer, Salactus, etc.

Describe the solution you'd like
Want documentation with sy

when following the example i get this error, i have the requirements.txt in the same folder as func.yaml

building /home/user/spec/func.yaml
Could not open requirements file: [Errno 2] No such file or directory: 'requirements.txt'
You are using pip version 10.0.1, however version 18.0 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
error running 

When following the "Connect app..." workflow in the Amplify Console with a GitHub.com repository, it's clear that the Amplify Console requires more than just read only access to the user's GitHub account yet the Amplify console sets conflicting expectations and the workshop module's README.md does not set the degree of access expectations with the user so that the user can make a more informed dec

If you'd like to have your company represented and are using Komiser please give formal written permission below via a comment and email to contact@komiser.io.

We will need a URL to a svg or png logo, a text title and a company URL.

Due to the security repercussions, of deploying this incorrectly, Are they any docs that go into more detail on a proper installation?

Background

Having added some streamalert-cli commands, the documentation on the command line via -h and ReadTheDocs varies and is laborious to maintain.

Description

A fantastic tool, to reduce this headache is sphinx-argparse. In short, it adds the ability to take an argparse parser and create documentation from the descriptions and everything else in the parser. A live e

I'm trying to follow the quick guide, I've done these steps:

1. serverless create -u https://github.com/adieuadieu/serverless-chrome/tree/master/examples/serverless-framework/aws
2. export AWS_PROFILE=serverless
3. npm run deploy

However at point 3, I'm not in the right folder am I?

If I cd aws and the run npm run deploy I get an error:

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

A very similar bug to #737 happens with the Account button in admin app when clicking outside of the button (see the blue arrow in the screenshot below). A pointer cursor is shown & the button's glowing animation is played regardless, as if it was functioning.

This is:

New AWS/Serverless users might not have AWS credentials setup in their machine, and they might not notice the .env documentations. They'd try to run a specific component, but AWS would return an unfriendly error.

For better DX, we should inform users that credentials are not found and they need to create a .env file.

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

Checklist

• [X ] Upgrade Jets: Are you using the latest version of Jets? This allows Jets to fix issues fast. There's a jets upgrade command that makes this a simple task. There's also an Upgrading Guide: http://rubyonjets.com/docs/upgrading/
• [ X] Reproducibility: Are you reporting a bug others will be able to reproduce and not asking a question. If you're unsure or want to ask a questi

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