You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+8-1Lines changed: 8 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,8 +2,15 @@
2
2
3
3
All notable changes to this project will be documented in this file.
4
4
5
+
## 1.2.0 - 2024-11-07
6
+
### Added features
7
+
- Added the ability to define tags for every resource created by the solution. This can be configured using the `configuration/solution_parameters/parameters.json` file.
8
+
9
+
### Changed
10
+
- Re-implemented the `safe_time_compare` feature to better accommodate scheduling execution delays and avoid data transfer duplications.
11
+
5
12
## 1.1.1 - 2024-10-25
6
-
###Bug Fixes
13
+
###Bug Fixes
7
14
- Fixed a typo on the CDK Stack preventing new deployments.
8
15
- Fixed an issue with the `sync_files` lambda function while comparing timestamps. For now the `safe_time_compare` feature is disabled until a better method can be implemented.
Copy file name to clipboardExpand all lines: README.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -193,6 +193,9 @@ This project is built using Python3 and CDK, before you start, make sure to have
193
193
194
194
## Deployment
195
195
196
+
### Tagging resources
197
+
By default the solution applies some native CDK and Name tags. If your deployment requires additional tags (for eg. Cost Allocation, Environment, Team, etc), you can now update the [solution parameters file](configuration/solution_parameters/parameters.json) by modifying the JSON for `additional_tags` with your specific Keys and Values.
198
+
196
199
### Permission Boundaries
197
200
If you are enforcing the usage of IAM Permission Boundaries for IAM Roles created in the account, you can update the [solution parameters file](configuration/solution_parameters/parameters.json) and add the managed policy ARN you are using to the `permission_boundary_policy_arn` parameter.
0 commit comments