diff --git a/test/samples/test-config.yaml b/test/samples/test-config.yaml index 5ac9dd3c..7e2475e4 100644 --- a/test/samples/test-config.yaml +++ b/test/samples/test-config.yaml @@ -1,170 +1,170 @@ Parameters: - queueName: testQueue + queueName: testQueue Tags: - stackset: testStackSet + stackset: testStackSet StackSet: - # A description of the stack set. You can use the description to identify the - # stack set's purpose or other important information. - description: "test description" + # A description of the stack set. You can use the description to identify the + # stack set's purpose or other important information. + description: "test description" - # In some cases, you must explicitly acknowledge that your stack set template - # contains certain capabilities in order for CloudFormation to create the stack - # set and related stack instances. - # - # * CAPABILITY_IAM and CAPABILITY_NAMED_IAM Some - # stack templates might include resources that can affect permissions in your - # Amazon Web Services account; for example, by creating new Identity and Access - # Management (IAM) users. For those stack sets, you must explicitly acknowledge - # this by specifying one of these capabilities. The following IAM resources - # require you to specify either the CAPABILITY_IAM or CAPABILITY_NAMED_IAM - # capability. - # - # * If you have IAM resources, you can specify either capability. - # - # * - # If you have IAM resources with custom names, you must specify - # CAPABILITY_NAMED_IAM. - # - # * If you don't specify either of these capabilities, - # CloudFormation returns an InsufficientCapabilities error. - # - # If your stack - # template contains these resources, we recommend that you review all permissions - # associated with them and edit their permissions if necessary. - # - # * - # AWS::IAM::AccessKey - # (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-iam-accesskey.html) - # - # * - # AWS::IAM::Group - # (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-iam-group.html) - # - # * - # AWS::IAM::InstanceProfile - # (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-iam-instanceprofile.html) - # - # * - # AWS::IAM::Policy - # (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-iam-policy.html) - # - # * - # AWS::IAM::Role - # (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-iam-role.html) - # - # * - # AWS::IAM::User - # (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-iam-user.html) - # - # * - # AWS::IAM::UserToGroupAddition - # (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-iam-addusertogroup.html) - # - # For - # more information, see Acknowledging IAM Resources in CloudFormation Templates - # (http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-iam-template.html#capabilities). - # - # * - # CAPABILITY_AUTO_EXPAND Some templates reference macros. If your stack set - # template references one or more macros, you must create the stack set directly - # from the processed template, without first reviewing the resulting changes in a - # change set. To create the stack set directly, you must acknowledge this - # capability. For more information, see Using CloudFormation Macros to Perform - # Custom Processing on Templates - # (http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/template-macros.html). - # Stack sets with service-managed permissions don't currently support the use of - # macros in templates. (This includes the AWS::Include - # (http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/create-reusable-transform-function-snippets-and-add-to-your-template-with-aws-include-transform.html) - # and AWS::Serverless - # (http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/transform-aws-serverless.html) - # transforms, which are macros hosted by CloudFormation.) Even if you specify this - # capability for a stack set with service-managed permissions, if you reference a - # macro in your template the stack set operation will fail. - capabilities: - - CAPABILITY_NAMED_IAM - - CAPABILITY_AUTO_EXPAND - - # The name of the IAM execution role to use to create the stack set. If you do not - # specify an execution role, CloudFormation uses the - # AWSCloudFormationStackSetExecutionRole role for the stack set operation. Specify - # an IAM role only if you are using customized execution roles to control which - # stack resources users and groups can include in their stack sets. - executionrolename: null - - # The Amazon Resource Number (ARN) of the IAM role to use to create this stack - # set. Specify an IAM role only if you are using customized administrator roles to - # control which users or groups can manage specific stack sets within the same - # administrator account. For more information, see Prerequisites: Granting - # Permissions for Stack Set Operations - # (http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-prereqs.html) - # in the CloudFormation User Guide. - administrationrolearn: null + # In some cases, you must explicitly acknowledge that your stack set template + # contains certain capabilities in order for CloudFormation to create the stack + # set and related stack instances. + # + # * CAPABILITY_IAM and CAPABILITY_NAMED_IAM Some + # stack templates might include resources that can affect permissions in your + # Amazon Web Services account; for example, by creating new Identity and Access + # Management (IAM) users. For those stack sets, you must explicitly acknowledge + # this by specifying one of these capabilities. The following IAM resources + # require you to specify either the CAPABILITY_IAM or CAPABILITY_NAMED_IAM + # capability. + # + # * If you have IAM resources, you can specify either capability. + # + # * + # If you have IAM resources with custom names, you must specify + # CAPABILITY_NAMED_IAM. + # + # * If you don't specify either of these capabilities, + # CloudFormation returns an InsufficientCapabilities error. + # + # If your stack + # template contains these resources, we recommend that you review all permissions + # associated with them and edit their permissions if necessary. + # + # * + # AWS::IAM::AccessKey + # (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-iam-accesskey.html) + # + # * + # AWS::IAM::Group + # (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-iam-group.html) + # + # * + # AWS::IAM::InstanceProfile + # (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-iam-instanceprofile.html) + # + # * + # AWS::IAM::Policy + # (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-iam-policy.html) + # + # * + # AWS::IAM::Role + # (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-iam-role.html) + # + # * + # AWS::IAM::User + # (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-iam-user.html) + # + # * + # AWS::IAM::UserToGroupAddition + # (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-iam-addusertogroup.html) + # + # For + # more information, see Acknowledging IAM Resources in CloudFormation Templates + # (http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-iam-template.html#capabilities). + # + # * + # CAPABILITY_AUTO_EXPAND Some templates reference macros. If your stack set + # template references one or more macros, you must create the stack set directly + # from the processed template, without first reviewing the resulting changes in a + # change set. To create the stack set directly, you must acknowledge this + # capability. For more information, see Using CloudFormation Macros to Perform + # Custom Processing on Templates + # (http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/template-macros.html). + # Stack sets with service-managed permissions don't currently support the use of + # macros in templates. (This includes the AWS::Include + # (http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/create-reusable-transform-function-snippets-and-add-to-your-template-with-aws-include-transform.html) + # and AWS::Serverless + # (http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/transform-aws-serverless.html) + # transforms, which are macros hosted by CloudFormation.) Even if you specify this + # capability for a stack set with service-managed permissions, if you reference a + # macro in your template the stack set operation will fail. + capabilities: + - CAPABILITY_NAMED_IAM + - CAPABILITY_AUTO_EXPAND - # Describes whether StackSets automatically deploys to Organizations accounts that - # are added to the target organization or organizational unit (OU). Specify only - # if PermissionModel is SERVICE_MANAGED. - autodeployment: null + # The name of the IAM execution role to use to create the stack set. If you do not + # specify an execution role, CloudFormation uses the + # AWSCloudFormationStackSetExecutionRole role for the stack set operation. Specify + # an IAM role only if you are using customized execution roles to control which + # stack resources users and groups can include in their stack sets. + executionrolename: null - # [Service-managed permissions] Specifies whether you are acting as an account - # administrator in the organization's management account or as a delegated - # administrator in a member account. By default, SELF is specified. Use SELF for - # stack sets with self-managed permissions. - # - # * To create a stack set with - # service-managed permissions while signed in to the management account, specify - # SELF. - # - # * To create a stack set with service-managed permissions while signed in - # to a delegated administrator account, specify DELEGATED_ADMIN. Your Amazon Web - # Services account must be registered as a delegated admin in the management - # account. For more information, see Register a delegated administrator - # (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-orgs-delegated-admin.html) - # in the CloudFormation User Guide. - # - # Stack sets with service-managed permissions - # are created in the management account, including stack sets that are created by - # delegated administrators. - callas: "" + # The Amazon Resource Number (ARN) of the IAM role to use to create this stack + # set. Specify an IAM role only if you are using customized administrator roles to + # control which users or groups can manage specific stack sets within the same + # administrator account. For more information, see Prerequisites: Granting + # Permissions for Stack Set Operations + # (http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-prereqs.html) + # in the CloudFormation User Guide. + administrationrolearn: null - # Describes whether StackSets performs non-conflicting operations concurrently and - # queues conflicting operations. - managedexecution: null + # Describes whether StackSets automatically deploys to Organizations accounts that + # are added to the target organization or organizational unit (OU). Specify only + # if PermissionModel is SERVICE_MANAGED. + autodeployment: null - # Describes how the IAM roles required for stack set operations are created. By - # default, SELF-MANAGED is specified. - # - # * With self-managed permissions, you must - # create the administrator and execution roles required to deploy to target - # accounts. For more information, see Grant Self-Managed Stack Set Permissions - # (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-prereqs-self-managed.html). - # - # * - # With service-managed permissions, StackSets automatically creates the IAM roles - # required to deploy to accounts managed by Organizations. For more information, - # see Grant Service-Managed Stack Set Permissions - # (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-prereqs-service-managed.html). - permissionmodel: "" + # [Service-managed permissions] Specifies whether you are acting as an account + # administrator in the organization's management account or as a delegated + # administrator in a member account. By default, SELF is specified. Use SELF for + # stack sets with self-managed permissions. + # + # * To create a stack set with + # service-managed permissions while signed in to the management account, specify + # SELF. + # + # * To create a stack set with service-managed permissions while signed in + # to a delegated administrator account, specify DELEGATED_ADMIN. Your Amazon Web + # Services account must be registered as a delegated admin in the management + # account. For more information, see Register a delegated administrator + # (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-orgs-delegated-admin.html) + # in the CloudFormation User Guide. + # + # Stack sets with service-managed permissions + # are created in the management account, including stack sets that are created by + # delegated administrators. + callas: "" -StackSetInstanses: - # [Service-managed permissions] The Organizations accounts for which to create - # stack instances in the specified Amazon Web Services Regions. You can specify - # Accounts or DeploymentTargets, but not both. - accounts: - - "577613639135" + # Describes whether StackSets performs non-conflicting operations concurrently and + # queues conflicting operations. + managedexecution: null - # The names of one or more Amazon Web Services Regions where you want to create - # stack instances using the specified Amazon Web Services accounts. - # - # This member is required. - regions: - - us-east-1 - - us-east-2 + # Describes how the IAM roles required for stack set operations are created. By + # default, SELF-MANAGED is specified. + # + # * With self-managed permissions, you must + # create the administrator and execution roles required to deploy to target + # accounts. For more information, see Grant Self-Managed Stack Set Permissions + # (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-prereqs-self-managed.html). + # + # * + # With service-managed permissions, StackSets automatically creates the IAM roles + # required to deploy to accounts managed by Organizations. For more information, + # see Grant Service-Managed Stack Set Permissions + # (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-prereqs-service-managed.html). + permissionmodel: "" - # [Service-managed permissions] The Organizations accounts for which to create - # stack instances in the specified Amazon Web Services Regions. You can specify - # Accounts or DeploymentTargets, but not both. - deploymenttargets: null +StackSetInstances: + # [Service-managed permissions] The Organizations accounts for which to create + # stack instances in the specified Amazon Web Services Regions. You can specify + # Accounts or DeploymentTargets, but not both. + accounts: + - "577613639135" - # Preferences for how CloudFormation performs this stack set operation. - operationpreferences: null \ No newline at end of file + # The names of one or more Amazon Web Services Regions where you want to create + # stack instances using the specified Amazon Web Services accounts. + # + # This member is required. + regions: + - us-east-1 + - us-east-2 + + # [Service-managed permissions] The Organizations accounts for which to create + # stack instances in the specified Amazon Web Services Regions. You can specify + # Accounts or DeploymentTargets, but not both. + deploymenttargets: null + + # Preferences for how CloudFormation performs this stack set operation. + operationpreferences: null