Skip to content

Commit 8df8501

Browse files
cmckni3cmckni3
committed
fix: Fix stackset sample template
- Convert tabs to spaces - Fix inconsistent indentation
1 parent 455f5f9 commit 8df8501

File tree

1 file changed

+157
-157
lines changed

1 file changed

+157
-157
lines changed

‎test/samples/test-config.yaml‎

Lines changed: 157 additions & 157 deletions
Original file line numberDiff line numberDiff line change
@@ -1,170 +1,170 @@
11
Parameters:
2-
queueName: testQueue
2+
queueName: testQueue
33
Tags:
4-
stackset: testStackSet
4+
stackset: testStackSet
55
StackSet:
66

7-
# A description of the stack set. You can use the description to identify the
8-
# stack set's purpose or other important information.
9-
description: "test description"
7+
# A description of the stack set. You can use the description to identify the
8+
# stack set's purpose or other important information.
9+
description: "test description"
1010

11-
# In some cases, you must explicitly acknowledge that your stack set template
12-
# contains certain capabilities in order for CloudFormation to create the stack
13-
# set and related stack instances.
14-
#
15-
# * CAPABILITY_IAM and CAPABILITY_NAMED_IAM Some
16-
# stack templates might include resources that can affect permissions in your
17-
# Amazon Web Services account; for example, by creating new Identity and Access
18-
# Management (IAM) users. For those stack sets, you must explicitly acknowledge
19-
# this by specifying one of these capabilities. The following IAM resources
20-
# require you to specify either the CAPABILITY_IAM or CAPABILITY_NAMED_IAM
21-
# capability.
22-
#
23-
# * If you have IAM resources, you can specify either capability.
24-
#
25-
# *
26-
# If you have IAM resources with custom names, you must specify
27-
# CAPABILITY_NAMED_IAM.
28-
#
29-
# * If you don't specify either of these capabilities,
30-
# CloudFormation returns an InsufficientCapabilities error.
31-
#
32-
# If your stack
33-
# template contains these resources, we recommend that you review all permissions
34-
# associated with them and edit their permissions if necessary.
35-
#
36-
# *
37-
# AWS::IAM::AccessKey
38-
# (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-iam-accesskey.html)
39-
#
40-
# *
41-
# AWS::IAM::Group
42-
# (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-iam-group.html)
43-
#
44-
# *
45-
# AWS::IAM::InstanceProfile
46-
# (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-iam-instanceprofile.html)
47-
#
48-
# *
49-
# AWS::IAM::Policy
50-
# (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-iam-policy.html)
51-
#
52-
# *
53-
# AWS::IAM::Role
54-
# (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-iam-role.html)
55-
#
56-
# *
57-
# AWS::IAM::User
58-
# (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-iam-user.html)
59-
#
60-
# *
61-
# AWS::IAM::UserToGroupAddition
62-
# (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-iam-addusertogroup.html)
63-
#
64-
# For
65-
# more information, see Acknowledging IAM Resources in CloudFormation Templates
66-
# (http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-iam-template.html#capabilities).
67-
#
68-
# *
69-
# CAPABILITY_AUTO_EXPAND Some templates reference macros. If your stack set
70-
# template references one or more macros, you must create the stack set directly
71-
# from the processed template, without first reviewing the resulting changes in a
72-
# change set. To create the stack set directly, you must acknowledge this
73-
# capability. For more information, see Using CloudFormation Macros to Perform
74-
# Custom Processing on Templates
75-
# (http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/template-macros.html).
76-
# Stack sets with service-managed permissions don't currently support the use of
77-
# macros in templates. (This includes the AWS::Include
78-
# (http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/create-reusable-transform-function-snippets-and-add-to-your-template-with-aws-include-transform.html)
79-
# and AWS::Serverless
80-
# (http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/transform-aws-serverless.html)
81-
# transforms, which are macros hosted by CloudFormation.) Even if you specify this
82-
# capability for a stack set with service-managed permissions, if you reference a
83-
# macro in your template the stack set operation will fail.
84-
capabilities:
85-
- CAPABILITY_NAMED_IAM
86-
- CAPABILITY_AUTO_EXPAND
87-
88-
# The name of the IAM execution role to use to create the stack set. If you do not
89-
# specify an execution role, CloudFormation uses the
90-
# AWSCloudFormationStackSetExecutionRole role for the stack set operation. Specify
91-
# an IAM role only if you are using customized execution roles to control which
92-
# stack resources users and groups can include in their stack sets.
93-
executionrolename: null
94-
95-
# The Amazon Resource Number (ARN) of the IAM role to use to create this stack
96-
# set. Specify an IAM role only if you are using customized administrator roles to
97-
# control which users or groups can manage specific stack sets within the same
98-
# administrator account. For more information, see Prerequisites: Granting
99-
# Permissions for Stack Set Operations
100-
# (http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-prereqs.html)
101-
# in the CloudFormation User Guide.
102-
administrationrolearn: null
11+
# In some cases, you must explicitly acknowledge that your stack set template
12+
# contains certain capabilities in order for CloudFormation to create the stack
13+
# set and related stack instances.
14+
#
15+
# * CAPABILITY_IAM and CAPABILITY_NAMED_IAM Some
16+
# stack templates might include resources that can affect permissions in your
17+
# Amazon Web Services account; for example, by creating new Identity and Access
18+
# Management (IAM) users. For those stack sets, you must explicitly acknowledge
19+
# this by specifying one of these capabilities. The following IAM resources
20+
# require you to specify either the CAPABILITY_IAM or CAPABILITY_NAMED_IAM
21+
# capability.
22+
#
23+
# * If you have IAM resources, you can specify either capability.
24+
#
25+
# *
26+
# If you have IAM resources with custom names, you must specify
27+
# CAPABILITY_NAMED_IAM.
28+
#
29+
# * If you don't specify either of these capabilities,
30+
# CloudFormation returns an InsufficientCapabilities error.
31+
#
32+
# If your stack
33+
# template contains these resources, we recommend that you review all permissions
34+
# associated with them and edit their permissions if necessary.
35+
#
36+
# *
37+
# AWS::IAM::AccessKey
38+
# (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-iam-accesskey.html)
39+
#
40+
# *
41+
# AWS::IAM::Group
42+
# (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-iam-group.html)
43+
#
44+
# *
45+
# AWS::IAM::InstanceProfile
46+
# (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-iam-instanceprofile.html)
47+
#
48+
# *
49+
# AWS::IAM::Policy
50+
# (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-iam-policy.html)
51+
#
52+
# *
53+
# AWS::IAM::Role
54+
# (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-iam-role.html)
55+
#
56+
# *
57+
# AWS::IAM::User
58+
# (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-iam-user.html)
59+
#
60+
# *
61+
# AWS::IAM::UserToGroupAddition
62+
# (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-iam-addusertogroup.html)
63+
#
64+
# For
65+
# more information, see Acknowledging IAM Resources in CloudFormation Templates
66+
# (http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-iam-template.html#capabilities).
67+
#
68+
# *
69+
# CAPABILITY_AUTO_EXPAND Some templates reference macros. If your stack set
70+
# template references one or more macros, you must create the stack set directly
71+
# from the processed template, without first reviewing the resulting changes in a
72+
# change set. To create the stack set directly, you must acknowledge this
73+
# capability. For more information, see Using CloudFormation Macros to Perform
74+
# Custom Processing on Templates
75+
# (http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/template-macros.html).
76+
# Stack sets with service-managed permissions don't currently support the use of
77+
# macros in templates. (This includes the AWS::Include
78+
# (http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/create-reusable-transform-function-snippets-and-add-to-your-template-with-aws-include-transform.html)
79+
# and AWS::Serverless
80+
# (http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/transform-aws-serverless.html)
81+
# transforms, which are macros hosted by CloudFormation.) Even if you specify this
82+
# capability for a stack set with service-managed permissions, if you reference a
83+
# macro in your template the stack set operation will fail.
84+
capabilities:
85+
- CAPABILITY_NAMED_IAM
86+
- CAPABILITY_AUTO_EXPAND
10387

104-
# Describes whether StackSets automatically deploys to Organizations accounts that
105-
# are added to the target organization or organizational unit (OU). Specify only
106-
# if PermissionModel is SERVICE_MANAGED.
107-
autodeployment: null
88+
# The name of the IAM execution role to use to create the stack set. If you do not
89+
# specify an execution role, CloudFormation uses the
90+
# AWSCloudFormationStackSetExecutionRole role for the stack set operation. Specify
91+
# an IAM role only if you are using customized execution roles to control which
92+
# stack resources users and groups can include in their stack sets.
93+
executionrolename: null
10894

109-
# [Service-managed permissions] Specifies whether you are acting as an account
110-
# administrator in the organization's management account or as a delegated
111-
# administrator in a member account. By default, SELF is specified. Use SELF for
112-
# stack sets with self-managed permissions.
113-
#
114-
# * To create a stack set with
115-
# service-managed permissions while signed in to the management account, specify
116-
# SELF.
117-
#
118-
# * To create a stack set with service-managed permissions while signed in
119-
# to a delegated administrator account, specify DELEGATED_ADMIN. Your Amazon Web
120-
# Services account must be registered as a delegated admin in the management
121-
# account. For more information, see Register a delegated administrator
122-
# (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-orgs-delegated-admin.html)
123-
# in the CloudFormation User Guide.
124-
#
125-
# Stack sets with service-managed permissions
126-
# are created in the management account, including stack sets that are created by
127-
# delegated administrators.
128-
callas: ""
95+
# The Amazon Resource Number (ARN) of the IAM role to use to create this stack
96+
# set. Specify an IAM role only if you are using customized administrator roles to
97+
# control which users or groups can manage specific stack sets within the same
98+
# administrator account. For more information, see Prerequisites: Granting
99+
# Permissions for Stack Set Operations
100+
# (http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-prereqs.html)
101+
# in the CloudFormation User Guide.
102+
administrationrolearn: null
129103

130-
# Describes whether StackSets performs non-conflicting operations concurrently and
131-
# queues conflicting operations.
132-
managedexecution: null
104+
# Describes whether StackSets automatically deploys to Organizations accounts that
105+
# are added to the target organization or organizational unit (OU). Specify only
106+
# if PermissionModel is SERVICE_MANAGED.
107+
autodeployment: null
133108

134-
# Describes how the IAM roles required for stack set operations are created. By
135-
# default, SELF-MANAGED is specified.
136-
#
137-
# * With self-managed permissions, you must
138-
# create the administrator and execution roles required to deploy to target
139-
# accounts. For more information, see Grant Self-Managed Stack Set Permissions
140-
# (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-prereqs-self-managed.html).
141-
#
142-
# *
143-
# With service-managed permissions, StackSets automatically creates the IAM roles
144-
# required to deploy to accounts managed by Organizations. For more information,
145-
# see Grant Service-Managed Stack Set Permissions
146-
# (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-prereqs-service-managed.html).
147-
permissionmodel: ""
109+
# [Service-managed permissions] Specifies whether you are acting as an account
110+
# administrator in the organization's management account or as a delegated
111+
# administrator in a member account. By default, SELF is specified. Use SELF for
112+
# stack sets with self-managed permissions.
113+
#
114+
# * To create a stack set with
115+
# service-managed permissions while signed in to the management account, specify
116+
# SELF.
117+
#
118+
# * To create a stack set with service-managed permissions while signed in
119+
# to a delegated administrator account, specify DELEGATED_ADMIN. Your Amazon Web
120+
# Services account must be registered as a delegated admin in the management
121+
# account. For more information, see Register a delegated administrator
122+
# (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-orgs-delegated-admin.html)
123+
# in the CloudFormation User Guide.
124+
#
125+
# Stack sets with service-managed permissions
126+
# are created in the management account, including stack sets that are created by
127+
# delegated administrators.
128+
callas: ""
148129

149-
StackSetInstanses:
150-
# [Service-managed permissions] The Organizations accounts for which to create
151-
# stack instances in the specified Amazon Web Services Regions. You can specify
152-
# Accounts or DeploymentTargets, but not both.
153-
accounts:
154-
- "577613639135"
130+
# Describes whether StackSets performs non-conflicting operations concurrently and
131+
# queues conflicting operations.
132+
managedexecution: null
155133

156-
# The names of one or more Amazon Web Services Regions where you want to create
157-
# stack instances using the specified Amazon Web Services accounts.
158-
#
159-
# This member is required.
160-
regions:
161-
- us-east-1
162-
- us-east-2
134+
# Describes how the IAM roles required for stack set operations are created. By
135+
# default, SELF-MANAGED is specified.
136+
#
137+
# * With self-managed permissions, you must
138+
# create the administrator and execution roles required to deploy to target
139+
# accounts. For more information, see Grant Self-Managed Stack Set Permissions
140+
# (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-prereqs-self-managed.html).
141+
#
142+
# *
143+
# With service-managed permissions, StackSets automatically creates the IAM roles
144+
# required to deploy to accounts managed by Organizations. For more information,
145+
# see Grant Service-Managed Stack Set Permissions
146+
# (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-prereqs-service-managed.html).
147+
permissionmodel: ""
163148

164-
# [Service-managed permissions] The Organizations accounts for which to create
165-
# stack instances in the specified Amazon Web Services Regions. You can specify
166-
# Accounts or DeploymentTargets, but not both.
167-
deploymenttargets: null
149+
StackSetInstances:
150+
# [Service-managed permissions] The Organizations accounts for which to create
151+
# stack instances in the specified Amazon Web Services Regions. You can specify
152+
# Accounts or DeploymentTargets, but not both.
153+
accounts:
154+
- "577613639135"
168155

169-
# Preferences for how CloudFormation performs this stack set operation.
170-
operationpreferences: null
156+
# The names of one or more Amazon Web Services Regions where you want to create
157+
# stack instances using the specified Amazon Web Services accounts.
158+
#
159+
# This member is required.
160+
regions:
161+
- us-east-1
162+
- us-east-2
163+
164+
# [Service-managed permissions] The Organizations accounts for which to create
165+
# stack instances in the specified Amazon Web Services Regions. You can specify
166+
# Accounts or DeploymentTargets, but not both.
167+
deploymenttargets: null
168+
169+
# Preferences for how CloudFormation performs this stack set operation.
170+
operationpreferences: null

0 commit comments

Comments
 (0)