chore: prepare release 1.0.11 (#500)

Author: OlafConijn

CHANGELOG.md

@@ -5,13 +5,13 @@ All notable changes to aws organization formation will be documented in this fil
 **BREAKING CHANGES**:
 - v1.0.0: execution role under which org-formation is ran requires the ec2:describeRegions permission 
 
-**version 1.0.11-beta.1**
+**version 1.0.11**
 - feat: support MaxConcurrentTasks > 0 on update-cdk tasks
 - feat: support IgnoreFileChanges on update-cdk, update-serverless.com and apply-tf tasks (allows the task to be skipped if certain files got changed)
 - fix: stacks in UPDATE_ROLLBACK_FAILED wont get deleted when attempting to recover from a failed update
 - feat: Control Tower (or any other account factory solution) support using the annotate-organization task
 
-**version 1.0.9**
+**version 1.0.9** / **version 1.0.10** (redeploy of 1.0.9)
 - feat: support `--match` and `--dev` on print & validate commands
 - feat: support serverless.com V3, by setting the `SLSVersion` attribute to `3` in the task file
 - fix: allow sub-expression to be a `!ReadFile`, `!Cmd` or other expression

docs/task-files.md

@@ -17,6 +17,7 @@
     - [!Include](#include)
   - [Task types](#task-types)
     - [update-organization](#update-organization)
+    - [annotate-organization](#annotate-organization)
     - [update-stacks](#update-stacks)
     - [update-serverless.com](#update-serverlesscom)
     - [copy-to-s3](#copy-to-s3)
@@ -282,6 +283,28 @@ The `update-organization` task will update all the organization resources based
 | Skip              | `true` or `false` | When `true` task (and dependent tasks) will not be executed. |
 | TemplatingContext | Dictionary        | Specifies the data for [templating](#templating).            |
 
+### annotate-organization
+
+The `annotate-organization` task will will allow you to use a different account factory (e.g. AWS Control Tower) while using org-formation to provision resources across the AWS Organization. If you use `annotate-organization`, you must use this *instead of* `update-organization`.
+
+| Attribute         | Value             | Remarks                                                      |
+| :---------------- | :---------------- | :----------------------------------------------------------- |
+| DefaultOrganizationAccessRoleName   | string     | The name of the Role used for cross account access (default is: `OrganizationAccountAccessRole`).                                   |
+| ExcludeAccounts   | List<string> | A list (array) of AWS Account Ids (string) that will be excluded from the org-formation provisioning process. These accounts will not be addressable using `!Ref AccountName` or bindings, such as `Account: *` |
+| AccountMapping    | Dictionary<string, string> | Dictionary where the AttributeName will be used as the Logical Name of the account, specified as Attribute value. When not specified, the account name is used as Logical Name.|
+
+example:
+``` yml
+AnnotateOrganization:
+  Type: annotate-organization
+  DefaultOrganizationAccessRoleName: OrganizationAccountAccessRole
+  ExcludeAccounts: ["123123123123", "123123123124"]
+  AccountMapping:
+    AccountA: "234234234234" # these mappings are optional, when specified the account can be referenced using `!Ref AccountA`
+    AccountB: "234234234235" # when not specified the account can be referenced using `!Ref My Account B` (or whatever the account name is)
+                             # regardless of this, accounts will always be included in bindings like `Account: *`
+```
+
 ### update-stacks
 
 The `update-stacks` task will provision all resources in all accounts specified in `Template`.

package.json

@@ -1,6 +1,6 @@
 {
   "name": "aws-organization-formation",
-  "version": "1.0.11-beta.1",
+  "version": "1.0.11",
   "description": "Infrastructure as code solution for AWS Organizations",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",