v0.15.0

Initial commit from internal repository.

.gitattributes

@@ -0,0 +1,6 @@
+# Set the default behavior, in case people don't have core.autocrlf set.
+* text=auto
+
+# Currently, this repository has LF dependencies in building and testing, with json, sh, and no extensions.
+# Until this is fixed, it is best to just set the whole repository to be LF.
+* eol=lf

.github/ISSUE_TEMPLATE/bug.md

@@ -0,0 +1,51 @@
+---
+name: "\U0001F41B Bug Report"
+about: Report a bug
+labels: bug, needs-triage
+---
+
+<!--
+description of the bug:
+-->
+
+
+
+
+### Reproduction Steps
+
+<!--
+minimal amount of code that causes the bug (if possible) or a reference:
+-->
+
+
+
+
+### Error Log
+
+<!--
+what is the error message you are seeing?
+-->
+
+
+
+
+### Environment
+
+  - **CDK CLI Version      :**
+  - **CDK Framework Version:**
+  - **RFDK Framework Version:**
+  - **Deadline Version:**
+  - **Node.js Version:** <!-- Version of Node.js (run the command `node -v`) -->
+  - **OS               :**
+  - **Language (Version):** <!-- [all | TypeScript (3.8.3) | Java (8)| Python (3.7.3) | etc... ] -->
+
+### Other
+
+<!-- e.g. detailed explanation, stacktraces, related issues, suggestions on how to fix, links for us to have context, eg. associated pull-request, stackoverflow, gitter, etc -->
+
+
+
+
+--- 
+
+This is :bug: Bug Report

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1 @@
+blank_issues_enabled: false

.github/ISSUE_TEMPLATE/doc.md

@@ -0,0 +1,27 @@
+---
+name: "📕 Documentation Issue"
+about: Issue in the reference documentation or developer guide
+labels: feature-request, documentation, needs-triage
+---
+
+<!-- 
+- want to help? submit a pull request here: https://github.com/aws/aws-rfdk
+-->
+
+<!--
+link to reference doc page:
+-->
+
+
+
+<!--
+describe your issue:
+-->
+
+
+
+
+
+---
+
+This is a 📕 documentation issue

.github/ISSUE_TEMPLATE/feature-request.md

@@ -0,0 +1,45 @@
+---
+name: "\U0001F680 Feature Request"
+about: Request a new feature
+labels: feature-request, needs-triage
+---
+
+<!-- short description of the feature you are proposing: -->
+
+
+
+
+
+### Use Case
+
+<!-- why do you need this feature? -->
+
+
+
+
+
+### Proposed Solution
+
+<!-- Please include prototype/workaround/sketch/reference implementation: -->
+
+
+
+
+
+### Other
+
+<!-- 
+e.g. detailed explanation, stacktraces, related issues, suggestions on how to fix, 
+links for us to have context, eg. associated pull-request, stackoverflow, gitter, etc
+-->
+
+
+
+
+
+* [ ] :wave: I may be able to implement this feature request
+* [ ] :warning: This feature might incur a breaking change
+
+---
+
+This is a :rocket: Feature Request

.github/ISSUE_TEMPLATE/general-issue.md

@@ -0,0 +1,36 @@
+---
+name: "\U00002753 General Issue"
+about: Create a new issue
+labels: needs-triage
+---
+
+<!-- NOTE:📕 If there is an issue regarding developer guide, please create an issue [here](https://github.com/awsdocs/aws-cdk-guide/issues) -->
+
+## :question: General Issue
+
+<!--
+⚠️ Important Information
+This repository's issues are intended for feature requests and bug reports.
+-->
+
+### The Question
+<!--
+Ask your question here. Include any details relevant. Make sure you are not
+falling prey to the [X/Y problem][2]!
+
+[2]: http://xyproblem.info
+-->
+
+### Environment
+
+  - **CDK CLI Version      :**
+  - **CDK Framework Version:**
+  - **RFDK Framework Version:**
+  - **Deadline Version:**
+  - **Node.js Version:** <!-- Version of Node.js (run the command `node -v`) -->
+  - **OS               :**
+  - **Language (Version):** <!-- [all | TypeScript (3.8.3) | Java (8)| Python (3.7.3) | etc... ] -->
+
+
+### Other information
+<!-- e.g. detailed explanation, stacktraces, related issues, suggestions on how to fix, links for us to have context, eg. associated pull-request, stackoverflow, gitter, etc -->

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,4 @@
+
+----
+
+*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

.github/README.md

@@ -0,0 +1,30 @@
+# Github Actions and Integration
+
+This directory is used to hold all templates and github actions that are integrated into the AWS RFDK Github Repository.
+
+## Pull Request Template
+
+This template currently only adds an affirmitive consent line to ensure that anyone who creates a pull request agrees with the Apache 2.0 License
+
+## Issue Templates
+
+We currently have the following 4 Issue Templates:
+
+* Bug
+* Doc
+* Feature Request
+* General Issue
+
+These all prepopulate the issue with questions to help get the information needed to assist with the issue.  They also add the initial labels to the issue so they will be easily sortable.
+
+## Workflows
+
+This folder contains the Github Actions that we have installed on the Git Repository.
+
+### Labeler
+
+This workflow is used to maintain the labels that are configured on the Git hub repository.
+
+It works by reading the file .github/config/labels.yml and updating the labels in repository so they match the labels described in that file.  This include updating existing labels, adding new labels, and removing all labels that do not exist in that file.
+
+This workflow is triggered whenever a change is pushed to the .github/config/labels.yml file in the mainline branch.

.github/config/labels.yml

@@ -0,0 +1,84 @@
+- name: bug
+  color: d73a4a
+  description: "This issue is a bug."
+- name: duplicate
+  color: cfd8d7
+  description: "This issue is a duplicate."
+- name: needs-triage
+  color: c7cafc
+  description: "This issue or PR still needs to be triaged."
+- name: investigating
+  color: 0000ff
+  description: "This issue is being investigated and/or work is in progress to resolve the issue."
+- name: response-requested
+  color: "666666"
+  description: "Waiting on additional info and feedback. Will move to 'closing-soon' in 7 days."
+- name: closing-soon
+  color: "000000"
+  description: "This issue will automatically close in 4 days unless further comments are made."
+- name: feature-request
+  color: 008672
+  description: "A feature should be added or improved."
+- name: guidance
+  color: 8a19e7
+  description: "Question that needs advice or information."
+- name: documentation
+  color: f7bc35
+  description: "This is a problem with documentation."
+- name: third-party
+  color: 40C8B6
+  description: "This issue is related to third-party libraries or applications."
+- name: dependencies
+  color: 40C8B6
+  description: "This issue is a problem in a dependency."
+- name: blocked
+  color: 86499B
+  description: "Work is blocked on this issue for this codebase. Other labels or comments may indicate why."
+- name: pending-release
+  color: 86499B
+  description: "This issue will be fixed by an approved PR that hasn't been released yet."
+- name: service-api
+  color: E06A18
+  description: "This issue is due to a problem in a service API, not the SDK implementation."
+- name: breaking-change
+  color: d85658
+  description: "This issue requires a breaking change to remediate."
+- name: needs-reproduction
+  color: ffe79b
+  description: "This issue needs reproduction."
+- name: needs-discussion
+  color: ffe79b
+  description: "This issue/PR requires more discussion with community."
+- name: SECURITY
+  color: d85658
+  description: ""
+- name: help wanted
+  color: ffe79b
+  description: "We are asking the community to submit a PR to resolve this issue."
+- name: wontfix
+  color: d85658
+  description: "We have determined that we will not resolve the issue"
+- name: pr/do-not-merge
+  color: 358F18
+  description: "This PR should not be merged at this time."
+- name: pr/breaking-change
+  color: 358F18
+  description: "This PR is a breaking change. It needs to be modified to be allowed in the current major version."   
+- name: pr/blocked
+  color: 358F18
+  description: "This PR cannot be merged or reviewed, because it is blocked for some reason."  
+- name: pr/work-in-progress
+  color: 358F18
+  description: "This PR is a draft and needs further work."  
+- name: pr/needs-review
+  color: 358F18
+  description: "This PR needs a review from a Member."  
+- name: pr/ready-to-merge
+  color: 358F18
+  description: "This PR is ready to be merged." 
+- name: pr/needs-tests
+  color: 358F18
+  description: "This PR is missing tests."  
+- name: contribution/core
+  color: DA5F98
+  description: "This is a PR that came from AWS."

.github/dependabot.yml

@@ -0,0 +1,17 @@
+# To get started with Dependabot version updates, you'll need to specify which
+# package ecosystems to update and where the package manifests are located.
+# Please see the documentation for all configuration options:
+# https://help.github.com/github/administering-a-repository/configuration-options-for-dependency-updates
+
+version: 2
+updates:
+  - package-ecosystem: "npm"
+    directory: "/" # Location of package manifests
+    schedule:
+      interval: "daily"
+    versioning-strategy: increase
+    ignore:
+      - dependency-name: "@types/node"
+        versions: ">=11.0.0-0"
+    commit-message:
+      prefix: "chore(deps):"

.github/workflows/labeler.yml

@@ -0,0 +1,26 @@
+name: labeler
+
+on:
+  push:
+    branches:
+      - mainline
+    paths:
+      - .github/config/labels.yml
+
+jobs:
+  modify-labels:
+    runs-on: ubuntu-latest
+    steps:
+      -
+        name: Checkout
+        uses: actions/checkout@v1
+      -
+        name: Run Labeler
+        if: success()
+        uses: crazy-max/ghaction-github-labeler@v2
+        with:
+          yaml_file: .github/config/labels.yml
+          skip_delete: false
+          dry_run: false
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.gitignore

@@ -0,0 +1,14 @@
+# TypeScript incremental build states
+*.tsbuildinfo
+# Root tsconfig.json (this gets auto-generated)
+/tsconfig.json
+# Dist folder used during build
+/dist
+
+node_modules/
+.tools/
+.BUILD_COMPLETED
+yarn-error.log
+
+#Defines license that must be present
+!license-header.js

.gitmessage

@@ -0,0 +1,31 @@
+<tag>(<module>): <subject> (Max 72 char, lowercase, no period at end)
+# Example:
+# feat(core): Implement automated commit messages
+
+# (Optional)
+# Commit message should describe motivation. Think about your code
+# reviewers and what information they need in order to understand what
+# you did. If it's a big commit (hopefully not), try to provide some
+# good entry points so it will be easier to follow.
+# |<----   Try To Limit Each Line to a Maximum Of 72 Characters   ---->|
+
+# (Optional)
+# If not obvious (i.e. from unit tests), describe how you verified that
+# your change works.
+# |<----   Try To Limit Each Line to a Maximum Of 72 Characters   ---->|
+
+# (Optional)
+# BREAKING CHANGE: <what broke and how to achieve this behavior now>
+# * **<module-name>:** <Another breaking change>
+# * **<module-name>:** <Yet another breaking change>
+#
+# If this commit includes breaking changes, they must be listed at the
+# end in the following format (markdown format):
+# |<----   Try To Limit Each Line to a Maximum Of 72 Characters   ---->|
+
+# --- COMMIT END ---
+# Tag can be 
+#    feat     (new feature)
+#    fix      (bug fix)
+#    refactor (refactoring code)
+#    chore (updating grunt tasks etc; no production code change)

.npmrc

@@ -0,0 +1,3 @@
+# Helps with using npm package-locally, while in a yarn workflow (avoids coupling scripts to yarn).
+# This is needed because yarn goes out of it's way to ensure it controls what `node` binary is used (for good!)
+scripts-prepend-node-path=auto