chore: update references to github/awslabs/ with github/aws/ (#3299)

After the organization move, update all github URLs with the new organization anchor.
aws · Jul 12, 2019 · f0fec54 · f0fec54
1 parent 39c10e7
commit f0fec54
Show file tree

Hide file tree

Showing 238 changed files with 1,364 additions and 1,249 deletions.
diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md
@@ -9,7 +9,7 @@ labels: needs-triage
   - [ ] :beetle: bug report
   - [ ] :rocket: feature request
   - [ ] :books: construct library gap
-  - [ ] :phone: security issue or vulnerability => Please see [policy](https://github.com/awslabs/aws-cdk/security/policy)
+  - [ ] :phone: security issue or vulnerability => Please see [policy](https://github.com/aws/aws-cdk/security/policy)
   - [ ] :question: support request => Please see note at the top of this template.
 
 
@@ -27,7 +27,7 @@ labels: needs-triage
 
 
 * **Please tell us about your environment:**
-  
+
   - CDK CLI Version: xx.xx.xx
   - Module Version: xx.xx.xx
   - OS: [all | Windows 10 | OSX Mojave | Ubuntu | etc... ]

diff --git a/.github/ISSUE_TEMPLATE/general-issues.md b/.github/ISSUE_TEMPLATE/general-issues.md
@@ -13,7 +13,7 @@ assignees: ''
   - [ ] :beetle: bug report
   - [ ] :rocket: feature request
   - [ ] :books: construct library gap
-  - [ ] :phone: security issue or vulnerability => Please see [policy](https://github.com/awslabs/aws-cdk/security/policy)
+  - [ ] :phone: security issue or vulnerability => Please see [policy](https://github.com/aws/aws-cdk/security/policy)
   - [ ] :question: support request => Please see note at the top of this template.
 
 
@@ -31,7 +31,7 @@ assignees: ''
 
 
 * **Please tell us about your environment:**
-  
+
   - CDK CLI Version: xx.xx.xx
   - Module Version: xx.xx.xx
   - OS: [all | Windows 10 | OSX Mojave | Ubuntu | etc... ]

diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
@@ -1,5 +1,5 @@
 ----
 
-Please read the [contribution guidelines](https://github.com/awslabs/aws-cdk/blob/master/CONTRIBUTING.md) and follow the pull-request checklist.
+Please read the [contribution guidelines](https://github.com/aws/aws-cdk/blob/master/CONTRIBUTING.md) and follow the pull-request checklist.
 
 *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
diff --git a/CHANGELOG.md b/CHANGELOG.md
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -159,7 +159,7 @@ BREAKING CHANGE: Description of what broke and how to achieve this behavior now
   same branch. Usually all these are going to be squashed when you merge to master. The commit messages should be hints
   for you when you finalize your merge commit message.
 * Make sure to update the PR title/description if things change. The PR title/description are going to be used as the
-  commit title/message and will appear in the CHANGELOG, so maintain them all the way throughout the process.  
+  commit title/message and will appear in the CHANGELOG, so maintain them all the way throughout the process.
 
 
 
@@ -176,7 +176,7 @@ The CDK is a big project, and, at the moment, all of the CDK modules are mastere
 to maintain integrity in the early stage of the project where things constantly change across the stack. In the future
 we believe many of these modules will be extracted to their own repositories.
 
-Another complexity is that the CDK is packaged using [jsii](https://github.com/awslabs/jsii) to multiple programming
+Another complexity is that the CDK is packaged using [jsii](https://github.com/aws/jsii) to multiple programming
 languages. This means that when a full build is complete, there will be a version of each module for each supported
 language.
 
@@ -317,7 +317,7 @@ This section includes step-by-step descriptions of common workflows.
 Clone the repo:
 
 ```console
-$ git clone [email protected]/awslabs/aws-cdk
+$ git clone [email protected]/aws/aws-cdk
 $ cd aws-cdk
 ```
 
@@ -341,7 +341,7 @@ $ ./pack.sh
 Clone the repo:
 
 ```console
-$ git clone [email protected]/awslabs/aws-cdk
+$ git clone [email protected]/aws/aws-cdk
 $ cd aws-cdk
 ```
 
@@ -545,5 +545,5 @@ $ CDK_TEST_BUILD=false lr test
 * [Samples](https://github.com/aws-samples/aws-cdk-examples): includes sample code in multiple languages
 * [Workshop](https://github.com/aws-samples/aws-cdk-intro-workshop): source for https://cdkworkshop.com
 * [Developer Guide](https://github.com/awsdocs/aws-cdk-guide): markdown source for developer guide
-* [jsii](https://github.com/awslabs/jsii): the technology we use for multi-language support. If you are looking to help us support new languages, start there.
+* [jsii](https://github.com/aws/jsii): the technology we use for multi-language support. If you are looking to help us support new languages, start there.
 
diff --git a/MANUAL_INSTALLATION.md b/MANUAL_INSTALLATION.md
@@ -8,7 +8,7 @@ The CDK is also distributed as a single zip file which contains:
 3. Java Framework and AWS Constructs
 
 You can download the zip file from the
-[Releases](http://github.com/awslabs/aws-cdk/releases) page on GitHub.
+[Releases](http://github.com/aws/aws-cdk/releases) page on GitHub.
 
 The zip file comes with a signature so the integrity of the download
 can be verified (see below).

diff --git a/README.md b/README.md
@@ -116,7 +116,7 @@ for tracking bugs and feature requests.
 * Come join the AWS CDK community on [Gitter](https://gitter.im/awslabs/aws-cdk)
 * Open a support ticket with [AWS Support](https://console.aws.amazon.com/support/home#/)
 * If it turns out that you may have found a bug,
-  please open an [issue](https://github.com/awslabs/aws-cdk/issues/new)
+  please open an [issue](https://github.com/aws/aws-cdk/issues/new)
 
 ## Contributing
 

diff --git a/design/aws-ecs/aws-ecs-autoscaling-queue-worker.md b/design/aws-ecs/aws-ecs-autoscaling-queue-worker.md
@@ -1,6 +1,6 @@
 # AWS ECS - L3 Construct for Autoscaling ECS/Fargate Service that Processes Items in a SQS Queue
 
-To address issue [#2396](https://github.com/awslabs/aws-cdk/issues/2396), the AWS ECS CDK construct library should provide a way for customers to create a queue processing service (an AWS ECS/Fargate service that processes items from an sqs queue). This would mean adding new ECS CDK constructs `QueueProcessingEc2Service` and `QueueProcessingFargateService`, that would take in the necessary properties required to create a task definition, an SQS queue as well as an ECS/Fargate service and enable autoscaling for the service based on cpu usage and the SQS queue's approximateNumberOfMessagesVisible metric.
+To address issue [#2396](https://github.com/aws/aws-cdk/issues/2396), the AWS ECS CDK construct library should provide a way for customers to create a queue processing service (an AWS ECS/Fargate service that processes items from an sqs queue). This would mean adding new ECS CDK constructs `QueueProcessingEc2Service` and `QueueProcessingFargateService`, that would take in the necessary properties required to create a task definition, an SQS queue as well as an ECS/Fargate service and enable autoscaling for the service based on cpu usage and the SQS queue's approximateNumberOfMessagesVisible metric.
 
 ## General approach
 

diff --git a/design/aws-ecs/aws-ecs-priv-registry-support.md b/design/aws-ecs/aws-ecs-priv-registry-support.md
@@ -1,12 +1,12 @@
 # AWS ECS - Support for Private Registry Authentication
 
-To address issue [#1698](https://github.com/awslabs/aws-cdk/issues/1698), the ECS construct library should provide a way for customers to specify [`repositoryCredentials`](https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ContainerDefinition.html#ECS-Type-ContainerDefinition-repositoryCredentials) on their container. 
+To address issue [#1698](https://github.com/aws/aws-cdk/issues/1698), the ECS construct library should provide a way for customers to specify [`repositoryCredentials`](https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ContainerDefinition.html#ECS-Type-ContainerDefinition-repositoryCredentials) on their container.
 
-Minimally, this would mean adding a new string field on `ContainerDefinition`, however this doesn't provide any added value in terms of logical grouping or resource creation. We can instead modify the existing ECS CDK construct [`ContainerImage`](https://github.com/awslabs/aws-cdk/blob/master/packages/%40aws-cdk/aws-ecs/lib/container-image.ts) so that repository credentials are specified along with the image they're meant to access.
+Minimally, this would mean adding a new string field on `ContainerDefinition`, however this doesn't provide any added value in terms of logical grouping or resource creation. We can instead modify the existing ECS CDK construct [`ContainerImage`](https://github.com/aws/aws-cdk/blob/master/packages/%40aws-cdk/aws-ecs/lib/container-image.ts) so that repository credentials are specified along with the image they're meant to access.
 
 ## General approach
 
-The [`ecs.ContainerImage`](https://github.com/awslabs/aws-cdk/blob/master/packages/%40aws-cdk/aws-ecs/lib/container-image.ts) class already includes constructs for 3 types of images:
+The [`ecs.ContainerImage`](https://github.com/aws/aws-cdk/blob/master/packages/%40aws-cdk/aws-ecs/lib/container-image.ts) class already includes constructs for 3 types of images:
 
 * DockerHubImage
 * EcrImage
@@ -16,20 +16,20 @@ DockerHub images are assumed public, however DockerHub also provides private rep
 
 There's also no explicit way to specify images hosted outside of DockerHub, AWS, or your local machine. Customers hosting their own registries or using another registry host, like Quay.io or JFrog Artifactory, would need to be able to specify both the image URI and the registry credentials in order to pull their images down for ECS tasks.
 
-Fundamentally, specifying images hosted in DockerHub or elsewhere works the same, because when passed an image URI vs. a plain (or namespaced) image name + tag, the Docker daemon does the right thing and tries to pull the image from the specified registery. 
+Fundamentally, specifying images hosted in DockerHub or elsewhere works the same, because when passed an image URI vs. a plain (or namespaced) image name + tag, the Docker daemon does the right thing and tries to pull the image from the specified registery.
 
 Therefore, we should rename the existing `DockerHubImage` type be more generic and add the ability to optionally specify credentials.
- 
+
 
 ## Code changes
 
 Given the above, we should make the following changes to support private registry authentication:
 
-1. Define `RepositoryCredentials` interface & class, add to `IContainerImage` 
-2. Rename `DockerHubImage` construct to be more generic, optionally accept and set `RepositoryCreds` 
+1. Define `RepositoryCredentials` interface & class, add to `IContainerImage`
+2. Rename `DockerHubImage` construct to be more generic, optionally accept and set `RepositoryCreds`
 
 
-# Part 1: How to define registry credentials 
+# Part 1: How to define registry credentials
 
 For extensibility, we can define a new `IRepositoryCreds` interface to house the AWS Secrets Manager secret with the creds and a new `RepositoryCreds` class which satisfies it using specific constructs (e.g., "fromSecret").
 

diff --git a/design/aws-ecs/aws-ecs-scheduled-ecs-task-construct.md b/design/aws-ecs/aws-ecs-scheduled-ecs-task-construct.md
@@ -1,6 +1,6 @@
 # AWS ECS - L3 Construct for Scheduling EC2 Tasks
 
-To address issue [#2352](https://github.com/awslabs/aws-cdk/issues/2352), the ECS CDK construct library should provide a way for customers to create a standalone scheduled task, without creating a service, for their container. The task will be initiated by a cloudwatch event that is scheduled based on [CW Scheduled Events](http://docs.aws.amazon.com/AmazonCloudWatch/latest/events/ScheduledEvents.html).
+To address issue [#2352](https://github.com/aws/aws-cdk/issues/2352), the ECS CDK construct library should provide a way for customers to create a standalone scheduled task, without creating a service, for their container. The task will be initiated by a cloudwatch event that is scheduled based on [CW Scheduled Events](http://docs.aws.amazon.com/AmazonCloudWatch/latest/events/ScheduledEvents.html).
 
 This would mean adding a new ECS CDK construct `ScheduledEc2Task`, that would take in the necessary properties required to create a Task Definition, an EventRuleTarget as well as an AWS EventRule.
 

diff --git a/design/aws-ecs/aws-ecs-service-discovery-integration.md b/design/aws-ecs/aws-ecs-service-discovery-integration.md
@@ -1,6 +1,6 @@
 # AWS ECS - Support for AWS Cloud Map (Service Discovery) Integration
 
-To address issue [#1554](https://github.com/awslabs/aws-cdk/issues/1554), the
+To address issue [#1554](https://github.com/aws/aws-cdk/issues/1554), the
 ECS construct library should provide a way to set
 [`serviceRegistries`](https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateService.html#ECS-CreateService-request-serviceRegistries)
 on their ECS service at the L1 level.

diff --git a/design/aws-guidelines.md b/design/aws-guidelines.md
@@ -24,7 +24,7 @@ etc, `IFoo` would be `IBucket`, `ITopic` and so forth.
 The guidelines in this document use TypeScript (and npm package names) since
 this is the source programming language used to author the library, which is
 later packaged and published to all programming languages through
-[jsii](https://github.com/awslabs/jsii).
+[jsii](https://github.com/aws/jsii).
 
 ## Modules
 

diff --git a/design/code-asset-metadata.md b/design/code-asset-metadata.md
@@ -1,6 +1,6 @@
 # RFC: AWS Lambda - Metadata about Code Assets
 
-As described in [#1432](https://github.com/awslabs/aws-cdk/issues/1432), in order to support local debugging,
+As described in [#1432](https://github.com/aws/aws-cdk/issues/1432), in order to support local debugging,
 debuggers like [SAM CLI](https://github.com/awslabs/aws-sam-cli) need to be able to find the code of a Lambda
 function locally.
 
@@ -57,7 +57,7 @@ well as through the key `assetMetadata` in `cdk.json`. Very similar design to ho
 We considered alternatives that will "enforce" the embedding of metadata when an asset is referenced by a resource. Since
 a single asset can be referenced by multiple resources, it means that the _relationship_ is what should trigger the
 metadata addition. There currently isn't support in the framework for such hooks, but there is a possiblility that
-the changes in [#1436](https://github.com/awslabs/aws-cdk/pull/1436) might enable hooking into the relationnship, and then we might be able to use this mechanism to produce the metadata.
+the changes in [#1436](https://github.com/aws/aws-cdk/pull/1436) might enable hooking into the relationnship, and then we might be able to use this mechanism to produce the metadata.
 
 Having said that, the need to embed asset metadata on resources is mainly confined to authors of L2 constructs, and not applicable for the general user population, so the value of automation is not high.
 

diff --git a/package.json b/package.json
@@ -23,7 +23,7 @@
   },
   "repository": {
     "type": "git",
-    "url": "git://github.com/awslabs/aws-cdk"
+    "url": "git://github.com/aws/aws-cdk"
   },
   "license": "Apache-2.0",
   "author": {

diff --git a/packages/@aws-cdk/alexa-ask/package.json b/packages/@aws-cdk/alexa-ask/package.json
@@ -33,10 +33,10 @@
   },
   "repository": {
     "type": "git",
-    "url": "https://github.com/awslabs/aws-cdk.git",
+    "url": "https://github.com/aws/aws-cdk.git",
     "directory": "packages/@aws-cdk/alexa-ask"
   },
-  "homepage": "https://github.com/awslabs/aws-cdk",
+  "homepage": "https://github.com/aws/aws-cdk",
   "scripts": {
     "build": "cdk-build",
     "integ": "cdk-integ",

diff --git a/packages/@aws-cdk/app-delivery/README.md b/packages/@aws-cdk/app-delivery/README.md
@@ -17,7 +17,7 @@
 
 This library includes a *CodePipeline* composite Action for deploying AWS CDK Applications.
 
-This module is part of the [AWS Cloud Development Kit](https://github.com/awslabs/aws-cdk) project.
+This module is part of the [AWS Cloud Development Kit](https://github.com/aws/aws-cdk) project.
 
 ### Limitations
 The construct library in it's current form has the following limitations:
@@ -78,7 +78,7 @@ pipeline.addStage({
 });
 
 const project = new codebuild.PipelineProject(pipelineStack, 'CodeBuild', {
-  /** 
+  /**
   * Choose an environment configuration that meets your use case.
   * For NodeJS, this might be:
   *
@@ -115,12 +115,12 @@ const deployServiceAAction = new cicd.PipelineDeployStackAction({
   stack: serviceStackA,
   input: synthesizedApp,
   // See the note below for details about this option.
-  adminPermissions: false, 
+  adminPermissions: false,
 });
 deployStage.addAction(deployServiceAAction);
 // Add the necessary permissions for you service deploy action. This role is
 // is passed to CloudFormation and needs the permissions necessary to deploy
-// stack. Alternatively you can enable [Administrator](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_job-functions.html#jf_administrator) permissions above, 
+// stack. Alternatively you can enable [Administrator](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_job-functions.html#jf_administrator) permissions above,
 // users should understand the privileged nature of this role.
 deployServiceAAction.addToRolePolicy(new iam.PolicyStatement({
     actions: ['service:SomeAction'],
@@ -165,7 +165,7 @@ artifacts:
   files: '**/*'
 ```
 
-The `PipelineDeployStackAction` expects it's `input` to contain the result of 
+The `PipelineDeployStackAction` expects it's `input` to contain the result of
 synthesizing a CDK App using the `cdk synth -o <directory>`.
 
 
diff --git a/packages/@aws-cdk/app-delivery/package.json b/packages/@aws-cdk/app-delivery/package.json
@@ -59,10 +59,10 @@
   },
   "repository": {
     "type": "git",
-    "url": "https://github.com/awslabs/aws-cdk.git",
+    "url": "https://github.com/aws/aws-cdk.git",
     "directory": "packages/@aws-cdk/app-delivery"
   },
-  "homepage": "https://github.com/awslabs/aws-cdk",
+  "homepage": "https://github.com/aws/aws-cdk",
   "license": "Apache-2.0",
   "author": {
     "name": "Amazon Web Services",

diff --git a/packages/@aws-cdk/assert/package.json b/packages/@aws-cdk/assert/package.json
@@ -38,15 +38,15 @@
     "source-map-support": "^0.5.12"
   },
   "repository": {
-    "url": "https://github.com/awslabs/aws-cdk.git",
+    "url": "https://github.com/aws/aws-cdk.git",
     "type": "git",
     "directory": "packages/@aws-cdk/assert"
   },
   "keywords": [
     "aws",
     "cdk"
   ],
-  "homepage": "https://github.com/awslabs/aws-cdk",
+  "homepage": "https://github.com/aws/aws-cdk",
   "engines": {
     "node": ">= 8.10.0"
   },

diff --git a/packages/@aws-cdk/assets/lib/staging.ts b/packages/@aws-cdk/assets/lib/staging.ts
@@ -16,7 +16,7 @@ export interface StagingProps extends CopyOptions {
  * by the CLI by default in order to ensure that when the CDK app exists, all
  * assets are available for deployment. Otherwise, if an app references assets
  * in temporary locations, those will not be available when it exists (see
- * https://github.com/awslabs/aws-cdk/issues/1716).
+ * https://github.com/aws/aws-cdk/issues/1716).
  *
  * The `stagedPath` property is a stringified token that represents the location
  * of the file or directory after staging. It will be resolved only during the

diff --git a/packages/@aws-cdk/assets/package.json b/packages/@aws-cdk/assets/package.json
@@ -30,7 +30,7 @@
   },
   "repository": {
     "type": "git",
-    "url": "https://github.com/awslabs/aws-cdk.git",
+    "url": "https://github.com/aws/aws-cdk.git",
     "directory": "packages/@aws-cdk/assets"
   },
   "scripts": {
@@ -78,7 +78,7 @@
     "@aws-cdk/cx-api": "^1.0.0",
     "minimatch": "^3.0.4"
   },
-  "homepage": "https://github.com/awslabs/aws-cdk",
+  "homepage": "https://github.com/aws/aws-cdk",
   "peerDependencies": {
     "@aws-cdk/core": "^1.0.0",
     "@aws-cdk/cx-api": "^1.0.0"

diff --git a/packages/@aws-cdk/aws-amazonmq/package.json b/packages/@aws-cdk/aws-amazonmq/package.json
@@ -33,10 +33,10 @@
   },
   "repository": {
     "type": "git",
-    "url": "https://github.com/awslabs/aws-cdk.git",
+    "url": "https://github.com/aws/aws-cdk.git",
     "directory": "packages/@aws-cdk/aws-amazonmq"
   },
-  "homepage": "https://github.com/awslabs/aws-cdk",
+  "homepage": "https://github.com/aws/aws-cdk",
   "scripts": {
     "build": "cdk-build",
     "integ": "cdk-integ",

diff --git a/packages/@aws-cdk/aws-amplify/README.md b/packages/@aws-cdk/aws-amplify/README.md
@@ -15,7 +15,7 @@
 ---
 <!--END STABILITY BANNER-->
 
-This module is part of the [AWS Cloud Development Kit](https://github.com/awslabs/aws-cdk) project.
+This module is part of the [AWS Cloud Development Kit](https://github.com/aws/aws-cdk) project.
 
 ```ts
 import amplify = require('@aws-cdk/aws-amplify');

diff --git a/packages/@aws-cdk/aws-amplify/package.json b/packages/@aws-cdk/aws-amplify/package.json
@@ -33,10 +33,10 @@
   },
   "repository": {
     "type": "git",
-    "url": "https://github.com/awslabs/aws-cdk.git",
+    "url": "https://github.com/aws/aws-cdk.git",
     "directory": "packages/@aws-cdk/aws-amplify"
   },
-  "homepage": "https://github.com/awslabs/aws-cdk",
+  "homepage": "https://github.com/aws/aws-cdk",
   "scripts": {
     "build": "cdk-build",
     "integ": "cdk-integ",

diff --git a/packages/@aws-cdk/aws-apigateway/README.md b/packages/@aws-cdk/aws-apigateway/README.md
@@ -468,4 +468,4 @@ new route53.ARecord(this, 'CustomDomainAliasRecord', {
 
 ----
 
-This module is part of the [AWS Cloud Development Kit](https://github.com/awslabs/aws-cdk) project.
+This module is part of the [AWS Cloud Development Kit](https://github.com/aws/aws-cdk) project.
diff --git a/packages/@aws-cdk/aws-apigateway/package.json b/packages/@aws-cdk/aws-apigateway/package.json
@@ -33,7 +33,7 @@
   },
   "repository": {
     "type": "git",
-    "url": "https://github.com/awslabs/aws-cdk.git",
+    "url": "https://github.com/aws/aws-cdk.git",
     "directory": "packages/@aws-cdk/aws-apigateway"
   },
   "scripts": {
@@ -82,7 +82,7 @@
     "@aws-cdk/aws-lambda": "^1.0.0",
     "@aws-cdk/core": "^1.0.0"
   },
-  "homepage": "https://github.com/awslabs/aws-cdk",
+  "homepage": "https://github.com/aws/aws-cdk",
   "peerDependencies": {
     "@aws-cdk/aws-certificatemanager": "^1.0.0",
     "@aws-cdk/aws-elasticloadbalancingv2": "^1.0.0",
Original file line number	Diff line number	Diff line change
Expand Up		@@ -468,4 +468,4 @@ new route53.ARecord(this, 'CustomDomainAliasRecord', {

		----

		This module is part of the [AWS Cloud Development Kit](https://github.com/awslabs/aws-cdk) project.
		This module is part of the [AWS Cloud Development Kit](https://github.com/aws/aws-cdk) project.