Skip to content

Commit cc8fbe2

Browse files
tabdunabitabdunabi
committed
Update to version v3.0.0
1 parent b22c523 commit cc8fbe2

File tree

131 files changed

+60393
-8099
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

131 files changed

+60393
-8099
lines changed

‎.github/ISSUE_TEMPLATE/bug_report.md

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
---
2+
name: Bug report
3+
about: Create a report to help us improve
4+
title: ""
5+
labels: bug
6+
assignees: ""
7+
---
8+
9+
**Describe the bug**
10+
11+
<!--- A clear and concise description of what the bug is -->
12+
13+
**To Reproduce**
14+
15+
<!--- Steps to reproduce the behavior -->
16+
17+
**Expected behavior**
18+
19+
<!--- A clear and concise description of what you expected to happen -->
20+
21+
**Please complete the following information about the solution:**
22+
23+
- [ ] Version: [e.g. v1.0.0]
24+
25+
To get the version of the solution, you can look at the description of the created CloudFormation stack. For example, "_(SO0009) - The AWS CloudFormation template for deployment of the aws-centralized-logging. Version v1.0.0_". You can also find the version from [releases](https://github.com/aws-solutions/aws-centralized-logging/releases)
26+
27+
- [ ] Region: [e.g. us-east-1]
28+
- [ ] Was the solution modified from the version published on this repository?
29+
- [ ] If the answer to the previous question was yes, are the changes available on GitHub?
30+
- [ ] Have you checked your [service quotas](https://docs.aws.amazon.com/general/latest/gr/aws_service_limits.html) for the sevices this solution uses?
31+
- [ ] Were there any errors in the CloudWatch Logs? [How to enable debug mode?](https://docs.aws.amazon.com/solutions/latest/serverless-transit-network-orchestrator/troubleshooting.html)
32+
33+
**Screenshots**
34+
If applicable, add screenshots to help explain your problem (please **DO NOT include sensitive information**).
35+
36+
**Additional context**
37+
Add any other context about the problem here.

‎.github/ISSUE_TEMPLATE/documentation-improvements.md

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
---
2+
name: Documentation improvements
3+
about: Suggest a documentation update
4+
title: ''
5+
labels: documentation
6+
assignees: ''
7+
8+
---
9+
10+
**What were you initially searching for in the docs?**
11+
<!--- Please help us understand how you looked for information that was either not available or unclear -->
12+
13+
**Is this related to an existing part of the documentation? Please share a link**
14+
15+
**Describe how we could make it clearer**
16+
17+
**If you have a proposed update, please share it here**

‎.github/ISSUE_TEMPLATE/feature_request.md

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
---
2+
name: Feature request
3+
about: Suggest an idea for this solution
4+
title: ''
5+
labels: feature-request, enhancement
6+
assignees: ''
7+
8+
---
9+
10+
**Is your feature request related to a problem? Please describe.**
11+
<!--- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
12+
13+
**Describe the feature you'd like**
14+
<!--- A clear and concise description of what you want to happen -->
15+
16+
**Additional context**
17+
<!--- Add any other context or screenshots about the feature request here -->

‎.github/PULL_REQUEST_TEMPLATE.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
*Issue #, if available:*
2+
3+
*Description of changes:*
4+
5+
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

‎.gitignore

Lines changed: 30 additions & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -1,34 +1,34 @@
1-
.DS_Store
2-
.idea/
1+
# Distribution folders
2+
global-s3-assets
3+
regional-s3-assets
4+
open-source
5+
6+
# Generated ouputs
7+
console-manifest.json
8+
dist
9+
.coverage
10+
coverage.xml
11+
*pycache*
12+
npm-debug.log
13+
*.zip
14+
*.xml
15+
reports
316
*.pyc
417
.eggs
518
*.egg-info
19+
.venv
620
.cache
7-
source/scratch/
8-
*.sonarlint
9-
**/.pytest_cache/
10-
**/pycache/
11-
**/__pycache__/
12-
/deployment/global-s3-assets/
13-
/deployment/regional-s3-assets/
14-
source/bin/
15-
source/pre-commit-hook.sh
16-
source/ui/node_modules
17-
source/ui/build
18-
source/ui/package-lock.json
19-
/source/botocore*
20-
/source/boto3*
21-
/source/dateutil/
22-
/source/python_dateutil*
23-
/source/docutils*
24-
/source/futures-*
25-
/source/jmespath*
26-
/source/concurrent/
27-
/source/s3transfer*
28-
/source/six-*
29-
/source/urllib3*
30-
/source/six.py
31-
/source/chardet*
32-
/source/certifi*
33-
/source/idna*
34-
/source/requests*
21+
.pytest_cache
22+
.mypy_cache
23+
.scannerwork
24+
build
25+
26+
# Node dependencies
27+
node_modules
28+
29+
# Misc
30+
.DS_Store
31+
.idea/
32+
*sonarlint*
33+
docs
34+
test.sh

‎CHANGELOG.md

Lines changed: 29 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,42 @@
11
# Change Log
2+
23
All notable changes to this project will be documented in this file.
34

45
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
56
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
67

7-
## [1.0.0] - 2019-09-10
8-
- Initial public release
8+
## [3.0.0] - 2022-03-25
9+
10+
### Added
11+
12+
- Tagging the Transit Gateway attachment with "Name" on both the hub and spoke accounts; with the account name, the AWS Organizations OU path and the VPC name
13+
- _ListOfVpcTagsForAttachment_ CloudFormation parameter to specify a comma separated list of tags which if found in the VPC, will be copied across to the TGW attachments
14+
- Support for Organizations Tag policies
15+
- STNO state machine [logging using CloudWatch logs](https://docs.aws.amazon.com/step-functions/latest/dg/cw-logs.html)
16+
17+
### Changed
18+
19+
- Improved reliability. Fixed race conditions (issue [#1](https://github.com/aws-solutions/serverless-transit-network-orchestrator/issues/1)).
20+
- Conditional auto-approval or auto-reject rules based on AWS Organizations OU membership, with separate rules for associations and propagations.
21+
- Events now logged in CloudWatch Logs in addition to DynamoDB; to enable searching with CloudWatch Log Insights
22+
- Allow VPCs deployed using CloudFormation, that has the STNO tags, to be deleted. This is done by triggering a deletion of the transit gateway attachment when CloudFormation attempts to delete the subnet.
23+
- Transit Gateway peering feature now implemented using AWS Lambda
24+
- Pinned dependency versions for deterministic builds
25+
26+
### Removed
27+
28+
- CloudFormation parameters for log retention days have been moved to _mappings_ section of the template
29+
- SSM Parameter Store for _UUID_ and _SendMetrics_ flag. Both now added as environment variable to lambda functions
30+
31+
## [2.0.0] - 2020-08-20
932

10-
## [2.0.0] - 2010-08-20
1133
- Ability to peer inter-region transit gateways by tagging the transit gateway.
1234
- Option to use an existing transit gateway.
1335
- Ability to create or use existing global network.
1436
- Register the transit gateway with the global network.
1537
- Ability to add custom CIDR blocks to the VPC route tables in the spoke accounts.
1638
- Ability to add customer-managed prefix lists to the VPC route tables in spoke accounts.
39+
40+
## [1.0.0] - 2019-09-10
41+
42+
- Initial public release

‎CONTRIBUTING.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ information to effectively respond to your bug report or contribution.
1111

1212
We welcome you to use the GitHub issue tracker to report bugs or suggest features.
1313

14-
When filing an issue, please check [existing open](https://github.com/awslabs/aws-serverless-transit-network-orchestrator/issues), or [recently closed](https://github.com/awslabs/aws-serverless-transit-network-orchestrator/issues?q=is%3Aissue+is%3Aclosed), issues to make sure somebody else hasn't already
14+
When filing an issue, please check [existing open](https://github.com/aws-solutions/aws-serverless-transit-network-orchestrator/issues), or [recently closed](https://github.com/aws-solutions/aws-serverless-transit-network-orchestrator/issues?q=is%3Aissue+is%3Aclosed), issues to make sure somebody else hasn't already
1515
reported the issue. Please try to include as much information as you can. Details like these are incredibly useful:
1616

1717
* A reproducible test case or series of steps
@@ -41,7 +41,7 @@ GitHub provides additional document on [forking a repository](https://help.githu
4141

4242

4343
## Finding contributions to work on
44-
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/awslabs/aws-serverless-transit-network-orchestrator/labels/help%20wanted) issues is a great place to start.
44+
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/aws-serverless-transit-network-orchestrator/labels/help%20wanted) issues is a great place to start.
4545

4646

4747
## Code of Conduct
@@ -55,7 +55,7 @@ If you discover a potential security issue in this project we ask that you notif
5555

5656

5757
## Licensing
58-
See the [LICENSE](https://github.com/awslabs/aws-serverless-transit-network-orchestrator/blob/master/LICENSE.txt) file for our project's licensing. We will ask you to confirm the licensing of your contribution.
58+
See the [LICENSE](https://github.com/aws-solutions/aws-serverless-transit-network-orchestrator/blob/master/LICENSE.txt) file for our project's licensing. We will ask you to confirm the licensing of your contribution.
5959

6060

6161
We may ask you to sign a [Contributor License Agreement (CLA)](http://en.wikipedia.org/wiki/Contributor_License_Agreement) for larger changes.

0 commit comments

Comments
 (0)