Merge pull request #1 from aws-solutions/release/v1.0.0

Update to release v1.0.0

Author: abhirpat

.env.example

@@ -0,0 +1,37 @@
+# Copy this file and rename to ".env" to save your local configuration outside of version control.
+# You should then be able to use the npm scripts that require these values.
+
+# Deployment Mode (Optional)
+# DEPLOYMENT_MODE="dev" # If set to "dev" deletion protection of stack resources is turned off.
+
+# Common
+HUB_ACCOUNT_ID=000000000000 # The AWS account that the Compute and Data stacks will be deployed to.
+NAMESPACE="myisb" # The namespace that the stacks will be deployed to.
+
+# Account Pool Stack CFN Parameters
+PARENT_OU_ID="ou-abcd-abcd1234" # The organization's root OU id is also acceptable.
+AWS_REGIONS="us-east-1,us-west-2" # The regions enabled in the sandbox accounts.
+
+# IDC Stack CFN Parameters
+IDENTITY_STORE_ID="d-0000000000" # The Identity Store Id of the Identity Source in IAM Identity Center.
+SSO_INSTANCE_ARN="arn:aws:sso:::instance/ssoins-0000000000000000" # The ARN of the SSO instance in IAM Identity Center.
+
+# Compute Stack CFN Parameters
+ORG_MGT_ACCOUNT_ID=000000000000 # The AWS account that the AccountPool stack is deployed to.
+IDC_ACCOUNT_ID=000000000000 # The AWS account that the IDC stack is deployed to.
+ACCEPT_SOLUTION_TERMS_OF_USE="" # Must be set to "Accept" for the compute stack to be deployed. Terms are located here ./source/infrastructure/lib/assets/terms-of-use.txt
+
+# Configuration Overrides (Optional)
+# NUKE_CONFIG_FILE_PATH="/example/path/nuke-config.yaml" # The file path for an alternative AWS Nuke configuration file to build the solution with.
+
+# Private ECR Repo Configs (Optional)
+# commands in package.json use HUB_ACCOUNT_ID for the account hosting ECR
+# PRIVATE_ECR_REPO="example-repo-name" # The private ECR repo name for hosting the account cleaner image.
+# PRIVATE_ECR_REPO_REGION="us-east-1" # Region for the private ECR repo being used.
+
+# E2E Test Configs (only required to run E2E test suite) (Optional)
+# DATA_STACK="InnovationSandbox-Data" # Name of the deployed Data stack.
+# COMPUTE_STACK="InnovationSandbox-Compute" # Name of the deployed Compute stack.
+# SANDBOX_ACCOUNT_ID="000000000000" # AWS account id to use for testing the account cleaner.
+# SANDBOX_ACCOUNT_ADMIN_ROLE_NAME="Admin" # The name of the administrative role to use in the test account.
+# EMAIL_FROM="[email protected]" # The email address to use for notifications during the e2e tests.

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,43 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ""
+labels: bug
+assignees: ""
+---
+
+**Describe the bug**
+
+<!--- A clear and concise description of what the bug is -->
+
+**To Reproduce**
+
+<!--- Steps to reproduce the behavior -->
+
+**Expected behavior**
+
+<!--- A clear and concise description of what you expected to happen -->
+
+**Please complete the following information about the solution:**
+
+- [ ] Version: [e.g. v1.0.0]
+
+To get the version of the solution, you can look at the description of the created
+CloudFormation stack. For example, _"(SO0284) Innovation Sandbox on AWS Stack, v1.0.0"_.
+
+- [ ] Region: [e.g. us-east-1]
+- [ ] Was the solution modified from the version published on this repository?
+- [ ] If the answer to the previous question was yes, are the changes available on
+      GitHub?
+- [ ] Have you checked your [service quotas]
+      (https://docs.aws.amazon.com/general/latest/gr/aws_service_limits.html)
+      for the sevices this solution uses?
+- [ ] Were there any errors in the CloudWatch Logs? [Troubleshooting]
+      (https link to troubleshooting in docs.aws.amazon.com for solution)
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem (please **DO NOT include
+sensitive information**).
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this solution
+title: ""
+labels: feature-request, enhancement
+assignees: ""
+---
+
+**Is your feature request related to a problem? Please describe.**
+
+<!--- A clear and concise description of what the problem is. Ex. I'm always
+frustrated when [...] -->
+
+**Describe the feature you'd like**
+
+<!--- A clear and concise description of what you want to happen -->
+
+**Additional context**
+
+<!--- Add any other context or screenshots about the feature request here -->

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,6 @@
+_Issue #, if available:_
+
+_Description of changes:_
+
+By submitting this pull request, I confirm that you can use, modify, copy, and
+redistribute this contribution, under the terms of your choice.

.gitignore

@@ -0,0 +1,37 @@
+*.js
+!jest.config.js
+*.d.ts
+!vite-env.d.ts
+node_modules/
+!source/.typescript/lambda/**/*.js
+!source/lambda/**/*.js
+dist
+bom.json
+.env
+
+# CDK asset staging directory
+.cdk.staging
+cdk.out
+
+deployment/global-s3-assets
+deployment/regional-s3-assets
+deployment/ecr
+open-source/
+staging/
+
+# Temporary folders
+tmp/
+temp/
+.temp_*/
+.build
+.test-reports
+
+### VisualStudioCode ###
+.vscode
+
+### macOS ###
+.DS_Store
+
+.idea
+
+**/coverage

.pre-commit-config.yaml

@@ -0,0 +1,74 @@
+# Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
+# SPDX-License-Identifier: Apache-2.0
+
+exclude: '^.*\.svg$'
+repos:
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v4.6.0
+    hooks:
+      - id: check-executables-have-shebangs
+        name: Check executables have shebangs
+      - id: fix-byte-order-marker
+        name: Fix byte order marker
+      - id: check-case-conflict
+        name: Check case conflict
+      - id: check-json
+        name: Check json
+      - id: check-yaml
+        name: Check yaml
+        args: [--allow-multiple-documents, --unsafe]
+      - id: check-toml
+        name: Check toml
+      - id: check-merge-conflict
+        name: Check for merge conflicts
+      - id: check-added-large-files
+        name: Check for added large files
+        exclude: |
+          (?x)^(
+            ^.*/package-lock.json |
+          )$
+      - id: end-of-file-fixer
+        name: Fix end of the files
+      - id: fix-encoding-pragma
+        name: Fix python encoding pragma
+      - id: trailing-whitespace
+        name: Trim trailing whitespace
+      - id: mixed-line-ending
+        name: Mixed line ending
+      - id: detect-private-key
+        name: Detect private keys
+  - repo: https://github.com/Lucas-C/pre-commit-hooks
+    rev: v1.5.5
+    hooks:
+      - id: insert-license
+        name: Insert license header (typescript and javascript)
+        files: \.tsx$|\.ts$|\.js$|\.jsx$|\.scss$
+        args:
+          - --license-filepath
+          - ./license_header.txt
+          - --comment-style
+          - // # defaults to Python's # syntax, requires changing for typescript syntax.
+          - --detect-license-in-X-top-lines=3
+  - repo: https://github.com/pre-commit/mirrors-prettier
+    rev: v3.1.0
+    hooks:
+      - id: prettier
+        name: Prettier
+        additional_dependencies:
+          - "prettier@^3.3.3"
+          - "@trivago/prettier-plugin-sort-imports"
+  - repo: https://github.com/koalaman/shellcheck-precommit
+    rev: v0.10.0
+    hooks:
+      - id: shellcheck
+        name: ShellChecker
+        args: ["-x", "--severity=warning"]
+        types: [shell]
+  # Local
+  - repo: local
+    hooks:
+      - id: detect-empty-files
+        name: Detect Empty Files
+        entry: scripts/detect-empty-files.sh
+        language: system
+        pass_filenames: false

CHANGELOG.md

@@ -0,0 +1,12 @@
+# Change Log
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [1.0.0] - 2025-05-22
+
+### Added
+
+- All files, initial version

CODE_OF_CONDUCT.md

@@ -1,4 +1,5 @@
 ## Code of Conduct
+
 This project has adopted the [Amazon Open Source Code of Conduct](https://aws.github.io/code-of-conduct).
 For more information see the [Code of Conduct FAQ](https://aws.github.io/code-of-conduct-faq) or contact
 [email protected] with any additional questions or comments.

CONTRIBUTING.md

@@ -6,24 +6,23 @@ documentation, we greatly value feedback and contributions from our community.
 Please read through this document before submitting any issues or pull requests to ensure we have all the necessary
 information to effectively respond to your bug report or contribution.
 
-
 ## Reporting Bugs/Feature Requests
 
 We welcome you to use the GitHub issue tracker to report bugs or suggest features.
 
-When filing an issue, please check existing open, or recently closed, issues to make sure somebody else hasn't already
+When filing an issue, please check [existing open](https://github.com/aws-solutions/innovation-sandbox-on-aws/issues), or [recently closed](https://github.com/aws-solutions/innovation-sandbox-on-aws/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aclosed%20), issues to make sure somebody else hasn't already
 reported the issue. Please try to include as much information as you can. Details like these are incredibly useful:
 
-* A reproducible test case or series of steps
-* The version of our code being used
-* Any modifications you've made relevant to the bug
-* Anything unusual about your environment or deployment
-
+- A reproducible test case or series of steps
+- The version of our code being used
+- Any modifications you've made relevant to the bug
+- Anything unusual about your environment or deployment
 
 ## Contributing via Pull Requests
+
 Contributions via pull requests are much appreciated. Before sending us a pull request, please ensure that:
 
-1. You are working against the latest source on the *main* branch.
+1. You are working against the latest source on the _main_ branch.
 2. You check existing open, and recently merged, pull requests to make sure someone else hasn't addressed the problem already.
 3. You open an issue to discuss any significant work - we would hate for your time to be wasted.
 
@@ -39,21 +38,22 @@ To send us a pull request, please:
 GitHub provides additional document on [forking a repository](https://help.github.com/articles/fork-a-repo/) and
 [creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
 
-
 ## Finding contributions to work on
-Looking at the existing issues is a great way to find something to contribute on. As our projects, by default, use the default GitHub issue labels (enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any 'help wanted' issues is a great place to start.
 
+Looking at the existing issues is a great way to find something to contribute on. As our projects, by default, use the default GitHub issue labels ((enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any ['help wanted'](https://github.com/aws-solutions/innovation-sandbox-on-aws/labels/help%20wanted) issues is a great place to start.
 
 ## Code of Conduct
+
 This project has adopted the [Amazon Open Source Code of Conduct](https://aws.github.io/code-of-conduct).
 For more information see the [Code of Conduct FAQ](https://aws.github.io/code-of-conduct-faq) or contact
 [email protected] with any additional questions or comments.
 
-
 ## Security issue notifications
-If you discover a potential security issue in this project we ask that you notify AWS/Amazon Security via our [vulnerability reporting page](http://aws.amazon.com/security/vulnerability-reporting/). Please do **not** create a public github issue.
 
+If you discover a potential security issue in this project we ask that you notify AWS/Amazon Security via our [vulnerability reporting page](http://aws.amazon.com/security/vulnerability-reporting/). Please do **not** create a public github issue.
 
 ## Licensing
 
-See the [LICENSE](LICENSE) file for our project's licensing. We will ask you to confirm the licensing of your contribution.
+See the [LICENSE](https://github.com/aws-solutions/innovation-sandbox-on-aws/blob/mainline/LICENSE) file for our project's licensing. We will ask you to confirm the licensing of your contribution.
+
+We may ask you to sign a [Contributor License Agreement (CLA)](https://en.wikipedia.org/wiki/Contributor_License_Agreement) for larger changes.