Skip to content

Commit 8386a8e

Browse files
VeetahaVeetaha
authored
Add Cloudformation -> CloudFormation typo to typos.toml (#113)
1 parent 49aee44 commit 8386a8e

File tree

10 files changed

+18
-17
lines changed

10 files changed

+18
-17
lines changed

‎.githooks/pre-commit‎

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -58,10 +58,8 @@ if command_exists ./node_modules/.bin/prettier; then
5858
echo "$files" | xargs ./node_modules/.bin/prettier --ignore-unknown --write
5959
fi
6060

61-
if command_exists tflint; then
62-
tflint --init
63-
tflint --config "$(pwd)/.tflint.hcl" --color --recursive
64-
fi
61+
# We don't have `tflint` in pre-commit hook because it doesn't ignore files
62+
# ignored in `.gitignore`. More details: https://github.com/terraform-linters/tflint/issues/2283
6563

6664
# Add the modified/prettified files to staging
6765
echo "$files" | xargs git add

‎asset-account/terraform/stack-set/examples/self-managed/README.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Self-Managed StackSet Example
22

3-
This is a basic example of using the `elastio-asset-account-stack-set` terraform module with the self-managed AWS Cloudformation StackSet.
3+
This is a basic example of using the `elastio-asset-account-stack-set` terraform module with the self-managed AWS CloudFormation StackSet.
44

55
You can deploy it even within a single account. Just specify the `template_url` input variable at minimum.
66

‎asset-account/terraform/stack-set/examples/service-managed/README.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Service-Managed StackSet Example
22

3-
This is a basic example of using the `elastio-asset-account-stack-set` terraform module with the service-managed AWS Cloudformation StackSet.
3+
This is a basic example of using the `elastio-asset-account-stack-set` terraform module with the service-managed AWS CloudFormation StackSet.
44

55
You'll need to deploy it from the AWS Management account. You'll also need to specify both the input variables: `accounts` and `organizational_unit_ids`.
66

‎codegen/src/policies/ElastioAssetAccountDeployer.ts‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -79,7 +79,7 @@ export default {
7979
Sid: "ElastioIamDelete",
8080
Action: ["iam:DeleteRole", "iam:DeletePolicy"],
8181

82-
// A name wildcard is required here because if Cloudformation tries to delete
82+
// A name wildcard is required here because if CloudFormation tries to delete
8383
// a non-existing resource with a Condition based on `elastio:resource` tag,
8484
// then it'll get a 403 AccessDenied error which it doesn't handle properly.
8585
// It stops the stack deletion process in a DELETE_FAILED state:

‎connector/terraform/README.md‎

Lines changed: 4 additions & 4 deletions
Large diffs are not rendered by default.

‎connector/terraform/modules/account/README.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# `elastio-connector-account` module
22

3-
Deploys an AWS Cloudformation stack named `elastio-account-level-stack`, which is deployed once per AWS account and contains the required IAM resources (roles, policies, etc.) for Elastio Connector to operate in the same account.
3+
Deploys an AWS CloudFormation stack named `elastio-account-level-stack`, which is deployed once per AWS account and contains the required IAM resources (roles, policies, etc.) for Elastio Connector to operate in the same account.
44

55
See the [`elastio-connector` module implementation](../../main.tf) for an example of how this module should be used.
66

@@ -59,7 +59,7 @@ No modules.
5959
| <a name="input_global_managed_policies"></a> [global_managed_policies](#input_global_managed_policies) | List of IAM managed policies ARNs to attach to all Elastio IAM roles | `set(string)` | `null` | no |
6060
| <a name="input_global_permission_boundary"></a> [global_permission_boundary](#input_global_permission_boundary) | The ARN of the IAM managed policy to use as a permission boundary for all Elastio IAM roles | `string` | `null` | no |
6161
| <a name="input_iam_resource_names_prefix"></a> [iam_resource_names_prefix](#input_iam_resource_names_prefix) | Add a custom prefix to names of all IAM resources deployed by this stack.<br/> The sum of the length of the prefix and suffix must not exceed 14 characters. | `string` | `null` | no |
62-
| <a name="input_iam_resource_names_static"></a> [iam_resource_names_static](#input_iam_resource_names_static) | If enabled, the stack will use static resource names without random characters in them.<br/><br/> This parameter is set to `true` by default, and it shouldn't be changed. The older<br/> versions of Elastio stack used random names generated by Cloudformation for IAM<br/> resources, which is inconvenient to work with. New deployments that use the terraform<br/> automation should have this set to `true` for easier management of IAM resources. | `bool` | `true` | no |
62+
| <a name="input_iam_resource_names_static"></a> [iam_resource_names_static](#input_iam_resource_names_static) | If enabled, the stack will use static resource names without random characters in them.<br/><br/> This parameter is set to `true` by default, and it shouldn't be changed. The older<br/> versions of Elastio stack used random names generated by CloudFormation for IAM<br/> resources, which is inconvenient to work with. New deployments that use the terraform<br/> automation should have this set to `true` for easier management of IAM resources. | `bool` | `true` | no |
6363
| <a name="input_iam_resource_names_suffix"></a> [iam_resource_names_suffix](#input_iam_resource_names_suffix) | Add a custom prefix to names of all IAM resources deployed by this stack.<br/> The sum of the length of the prefix and suffix must not exceed 14 characters. | `string` | `null` | no |
6464
| <a name="input_lambda_tracing"></a> [lambda_tracing](#input_lambda_tracing) | Enable AWS X-Ray tracing for Lambda functions. This increases the cost of<br/> the stack. Enable only if needed | `bool` | `null` | no |
6565
| <a name="input_network_configuration"></a> [network_configuration](#input_network_configuration) | Can be set to either `Auto` or `Manual`. If set to `Auto`, Elastio will<br/> automatically create a VPC and subnets in the specified regions for the<br/> scan clusters to run in.<br/><br/> If set to `Manual`, you must provide the `vpc_id` and `subnet_ids` in the<br/> `region` module with the network config for each region. | `string` | `"Auto"` | no |

‎connector/terraform/modules/account/variables.tf‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -147,7 +147,7 @@ variable "iam_resource_names_static" {
147147
If enabled, the stack will use static resource names without random characters in them.
148148
149149
This parameter is set to `true` by default, and it shouldn't be changed. The older
150-
versions of Elastio stack used random names generated by Cloudformation for IAM
150+
versions of Elastio stack used random names generated by CloudFormation for IAM
151151
resources, which is inconvenient to work with. New deployments that use the terraform
152152
automation should have this set to `true` for easier management of IAM resources.
153153
DESCR

‎connector/terraform/modules/nat-provision/README.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# `elastio-nat-provision` module
22

3-
Creates an AWS Cloudformation stack named `elastio-nat-provision-lambda` which deploys NAT gateways in the private subnets where Elastio scan job workers run. This is necessary only if you deploy Elastio into private subnets that don't have outbound Internet access already. Alternatively, you can deploy your own NAT gateway if you want to.
3+
Creates an AWS CloudFormation stack named `elastio-nat-provision-lambda` which deploys NAT gateways in the private subnets where Elastio scan job workers run. This is necessary only if you deploy Elastio into private subnets that don't have outbound Internet access already. Alternatively, you can deploy your own NAT gateway if you want to.
44

55
See the [`elastio-connector` module implementation](../../main.tf) for an example of how this module should be used.
66

‎connector/terraform/variables.tf‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,7 @@ variable "elastio_nat_provision_stack" {
7272
description = <<DESCR
7373
Specifies the version of Elastio NAT provision stack to deploy (e.g. `v5`).
7474
75-
This is a Cloudformation stack that automatically provisions NAT Gateways in
75+
This is a CloudFormation stack that automatically provisions NAT Gateways in
7676
your VPC when Elastio worker instances run to provide them with the outbound
7777
Internet access when Elastio is deployed in private subnets.
7878
@@ -173,7 +173,7 @@ variable "iam_resource_names_static" {
173173
If enabled, the stack will use static resource names without random characters in them.
174174
175175
This parameter is set to `true` by default, and it shouldn't be changed. The older
176-
versions of Elastio stack used random names generated by Cloudformation for IAM
176+
versions of Elastio stack used random names generated by CloudFormation for IAM
177177
resources, which is inconvenient to work with. New deployments that use the terraform
178178
automation should have this set to `true` for easier management of IAM resources.
179179
DESCR

‎typos.toml‎

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
[default.extend-identifiers]
2+
3+
Cloudformation = "CloudFormation"

0 commit comments

Comments
 (0)