Remove serverless.com mentions to avoid confusing users on the brand or ownership of the project

mnapoli · mnapoli · commit b5b0ddbda9ec · 2024-09-23T15:01:32.000+02:00
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
@@ -55,7 +55,7 @@ further defined and clarified by project maintainers.
 ## Enforcement
 
 Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting our team at **hello@serverless.com**. As an alternative
+reported by contacting our team on GitHub. As an alternative
 feel free to reach out to any of us personally. All
 complaints will be reviewed and investigated and will result in a response that
 is deemed necessary and appropriate to the circumstances. The project team is
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
diff --git a/docs/events/README.md b/docs/events/README.md
@@ -5,5 +5,3 @@ Welcome to the AWS Serverless Events Glossary.
 Please select a section on the left to get started, or see the [user
 guide](../guides/events.md) for general information regarding Lambda Events in
 Serverless.
-
-If you have questions, join the [Slack community](https://serverless.com/slack) or [post over on the forums](https://forum.serverless.com/)
diff --git a/docs/events/apigateway.md b/docs/events/apigateway.md
@@ -1060,7 +1060,7 @@ functions:
 
 #### Pass Through Behavior
 
-[API Gateway](https://serverless.com/amazon-api-gateway/) provides multiple ways to handle requests where the Content-Type header does not match any of the specified mapping templates. When this happens, the request payload will either be passed through the integration request _without transformation_ or rejected with a `415 - Unsupported Media Type`, depending on the configuration.
+API Gateway provides multiple ways to handle requests where the Content-Type header does not match any of the specified mapping templates. When this happens, the request payload will either be passed through the integration request _without transformation_ or rejected with a `415 - Unsupported Media Type`, depending on the configuration.
 
 You can define this behaviour as follows (if not specified, a value of **NEVER** will be used):
 
@@ -1242,7 +1242,7 @@ functions:
 ## Setting an HTTP Proxy on API Gateway
 
 To set up an HTTP proxy, you'll need two CloudFormation templates, one for the endpoint (known as resource in CF), and
-one for method. These two templates will work together to construct your proxy. So if you want to set `your-app.com/serverless` as a proxy for `serverless.com`, you'll need the following two templates in your `serverless.yml`:
+one for method. These two templates will work together to construct your proxy. So if you want to set `your-app.com/serverless` as a proxy for `example.com`, you'll need the following two templates in your `serverless.yml`:
 
 ```yml
 service: service-name
@@ -1274,7 +1274,7 @@ resources:
         Integration:
           IntegrationHttpMethod: POST
           Type: HTTP
-          Uri: http://serverless.com # the URL you want to set a proxy to
+          Uri: http://example.com # the URL you want to set a proxy to
           IntegrationResponses:
             - StatusCode: 200
 ```
diff --git a/docs/events/cloudfront.md b/docs/events/cloudfront.md
@@ -23,7 +23,7 @@ Lambda@Edge has four options when the Lambda function is triggered
 
 **RUNTIME LIMITS:** According to [AWS Requirements on Lambda@Edge](https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/lambda-requirements-limits.html) the runtimes supported by Lambda@Edge functions are: `Python 3.9`, `Python 3.8`, `Python 3.7`, `Node.js 16.x`, `Node.js 14.x`, `Node.js 12.x`, `Node.js 10.x`.
 
-**FUNCTION SIZE LIMITS:** According to [AWS Quotas on CloudFront](https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/cloudfront-limits.html#limits-functions), Lambda@Edge functions mustn't exceed the maximum size of 10KB. An easy way of reducing the size of a function is through bundling and minification via e.g. the plugin [serverless-esbuild](https://www.serverless.com/plugins/serverless-esbuild).
+**FUNCTION SIZE LIMITS:** According to [AWS Quotas on CloudFront](https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/cloudfront-limits.html#limits-functions), Lambda@Edge functions mustn't exceed the maximum size of 10KB. An easy way of reducing the size of a function is through bundling and minification via e.g. the plugin [serverless-esbuild](https://www.example.com/plugins/serverless-esbuild).
 
 ## Simple event definition
 
@@ -67,7 +67,7 @@ functions:
           eventType: viewer-response
           pathPattern: /docs*
           origin:
-            DomainName: serverless.com
+            DomainName: example.com
             OriginPath: /framework
             CustomOriginConfig:
               OriginProtocolPolicy: match-viewer
@@ -94,7 +94,7 @@ functions:
           eventType: viewer-response
           pathPattern: /docs*
           origin:
-            DomainName: serverless.com
+            DomainName: example.com
             OriginPath: /framework
             CustomOriginConfig:
               OriginProtocolPolicy: match-viewer
@@ -120,7 +120,7 @@ functions:
 custom:
   origins:
     myWebsiteOrigin:
-      DomainName: serverless.com
+      DomainName: example.com
       OriginPath: /framework
       CustomOriginConfig:
         OriginProtocolPolicy: match-viewer
@@ -141,7 +141,7 @@ functions:
           eventType: viewer-response
           pathPattern: /docs*
           origin:
-            DomainName: serverless.com
+            DomainName: example.com
             OriginPath: /framework
             CustomOriginConfig:
               OriginProtocolPolicy: match-viewer
diff --git a/docs/events/streams.md b/docs/events/streams.md
@@ -2,7 +2,7 @@
 
 This setup specifies that the `compute` function should be triggered whenever:
 
-1. the corresponding [DynamoDB](https://serverless.com/dynamodb/) table is modified (e.g. a new entry is added).
+1. the corresponding DynamoDB table is modified (e.g. a new entry is added).
 2. the Lambda checkpoint has not reached the end of the Kinesis stream (e.g. a new record is added).
 
 The ARN for the stream can be specified as a string, the reference to the ARN of a resource by logical ID, or the import of an ARN that was exported by a different service or CloudFormation stack.
diff --git a/docs/guides/events.md b/docs/guides/events.md
@@ -2,7 +2,7 @@
 
 Simply put, events are the things that trigger your functions to run.
 
-If you are using AWS as your provider, all `events` in the service are anything in AWS that can trigger an AWS Lambda function, like an S3 bucket upload, an SNS topic, and HTTP endpoints created via [API Gateway](https://serverless.com/amazon-api-gateway/).
+If you are using AWS as your provider, all `events` in the service are anything in AWS that can trigger an AWS Lambda function, like an S3 bucket upload, an SNS topic, and HTTP endpoints created via API Gateway.
 
 [View the AWS events section for a list of supported events](../events)
 
diff --git a/docs/guides/functions.md b/docs/guides/functions.md
@@ -526,7 +526,7 @@ The Lambda function execution role must have permissions to create, describe and
 
 **VPC Lambda Internet Access**
 
-By default, when a Lambda function is executed inside a VPC, it loses internet access and some resources inside AWS may become unavailable. In order for S3 resources and [DynamoDB](https://serverless.com/dynamodb/) resources to be available for your Lambda function running inside the VPC, a VPC end point needs to be created. For more information please check [VPC Endpoint for Amazon S3](https://aws.amazon.com/blogs/aws/new-vpc-endpoint-for-amazon-s3/).
+By default, when a Lambda function is executed inside a VPC, it loses internet access and some resources inside AWS may become unavailable. In order for S3 resources and DynamoDB resources to be available for your Lambda function running inside the VPC, a VPC end point needs to be created. For more information please check [VPC Endpoint for Amazon S3](https://aws.amazon.com/blogs/aws/new-vpc-endpoint-for-amazon-s3/).
 In order for other services such as Kinesis streams to be made available, a NAT Gateway needs to be configured inside the subnets that are being used to run the Lambda, for the VPC used to execute the Lambda. For more information, please check [Enable Outgoing Internet Access within VPC](https://medium.com/@philippholly/aws-lambda-enable-outgoing-internet-access-within-vpc-8dd250e11e12)
 
 ## Environment Variables
@@ -698,7 +698,7 @@ We're working on a fix so that SQS queue arns will be supported in the future.
 
 ## KMS Keys
 
-[AWS Lambda](https://serverless.com/aws-lambda/) uses [AWS Key Management Service (KMS)](https://aws.amazon.com/kms/) to encrypt your environment variables at rest.
+AWS Lambda uses [AWS Key Management Service (KMS)](https://aws.amazon.com/kms/) to encrypt your environment variables at rest.
 
 The `kmsKeyArn` config variable enables you a way to define your own KMS key which should be used for encryption.
 
diff --git a/docs/guides/intro.md b/docs/guides/intro.md
@@ -1,6 +1,6 @@
 # Serverless Framework Concepts
 
-The Serverless Framework helps you develop and deploy [AWS Lambda](https://serverless.com/aws-lambda/) functions, along with the AWS infrastructure resources they require. It's a CLI that offers structure, automation and best practices out-of-the-box, allowing you to focus on building sophisticated, event-driven, serverless architectures, comprised of [Functions](#functions) and [Events](#events).
+The Serverless Framework helps you develop and deploy AWS Lambda functions, along with the AWS infrastructure resources they require. It's a CLI that offers structure, automation and best practices out-of-the-box, allowing you to focus on building sophisticated, event-driven, serverless architectures, comprised of [Functions](#functions) and [Events](#events).
 
 The Serverless Framework is different from other application frameworks because:
 
diff --git a/docs/guides/serverless.yml.md b/docs/guides/serverless.yml.md
@@ -1295,7 +1295,7 @@ functions:
             # Refers to any external Cache Policy ID
             id: 658327ea-f89d-4fab-a63d-7e88639e58f6
           origin:
-            DomainName: serverless.com
+            DomainName: example.com
             OriginPath: /framework
             CustomOriginConfig:
               OriginProtocolPolicy: match-viewer
diff --git a/docs/guides/variables.md b/docs/guides/variables.md
@@ -145,7 +145,7 @@ In the above example you're dynamically adding a prefix to the function names by
 
 ## Referencing Parameters
 
-Parameters can be defined in `serverless.yml` under the `params` key, or in [Serverless Dashboard](https://www.serverless.com/secrets).
+Parameters can be defined in `serverless.yml` under the `params` key, or passed in as CLI arguments.
 
 To reference parameters, use the `${param:XXX}` syntax in `serverless.yml`.
 
diff --git a/lib/classes/cli.js b/lib/classes/cli.js
@@ -1,7 +1,5 @@
 'use strict';
 
-const version = require('../../package.json').version;
-const os = require('os');
 const chalk = require('chalk');
 const { log } = require('@serverless/utils/log');
 const resolveCliInput = require('../cli/resolve-input');
@@ -30,20 +28,6 @@ class CLI {
     return true;
   }
 
-  asciiGreeting() {
-    let art = '';
-    art = `${art} _______                             __${os.EOL}`;
-    art = `${art}|   _   .-----.----.--.--.-----.----|  .-----.-----.-----.${os.EOL}`;
-    art = `${art}|   |___|  -__|   _|  |  |  -__|   _|  |  -__|__ --|__ --|${os.EOL}`;
-    art = `${art}|____   |_____|__|  \\___/|_____|__| |__|_____|_____|_____|${os.EOL}`;
-    art = `${art}|   |   |             The Serverless Application Framework${os.EOL}`;
-    art = `${art}|       |                           serverless.com, v${version}${os.EOL}`;
-    art = `${art} -------'`;
-
-    this.consoleLog(chalk.yellow(art));
-    this.consoleLog('');
-  }
-
   printDot() {
     process.stdout.write(chalk.yellow('.'));
   }
diff --git a/lib/classes/config-schema-handler/index.js b/lib/classes/config-schema-handler/index.js
@@ -77,18 +77,6 @@ class ConfigSchemaHandler {
   async validateConfig(userConfig) {
     if (!this.schema.properties.provider.properties.name) {
       configurationValidationResults.set(this.serverless.configurationInput, false);
-      if (this.serverless.service.configValidationMode !== 'off') {
-        log.warning(
-          [
-            `You're relying on provider "${this.serverless.service.provider.name}" defined by a plugin which doesn't provide a validation schema for its config.`,
-            `Please report the issue at its bug tracker linking: ${style.link(
-              'https://www.serverless.com/framework/docs/providers/aws/guide/plugins#extending-validation-schema'
-            )}`,
-            'You may turn off this message with "configValidationMode: off" setting',
-            '',
-          ].join('\n')
-        );
-      }
 
       this.relaxProviderSchema();
     }
diff --git a/lib/utils/log-deprecation.js b/lib/utils/log-deprecation.js
diff --git a/test/integration/aws/function-url.test.js b/test/integration/aws/function-url.test.js
diff --git a/test/integration/aws/http-api.test.js b/test/integration/aws/http-api.test.js
diff --git a/test/unit/lib/plugins/aws/package/compile/events/http-api.test.js b/test/unit/lib/plugins/aws/package/compile/events/http-api.test.js
diff --git a/test/unit/lib/utils/fs/parse.test.js b/test/unit/lib/utils/fs/parse.test.js
