Reword "infrastructure_only" option

Author: arm4b

README.md

@@ -74,7 +74,7 @@ The following inputs can be used as `steps.with` keys:
 | `aws_ec2_instance_profile` | string | | [The AWS IAM instance profile](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_switch-role-ec2_instance-profiles.html) to use for the EC2 instance. Use if you want to pass an AWS role with specific permissions granted to the instance |
 | `aws_resource_identifier` | string | `${org}-${repo}-${branch}` | Auto-generated by default so it's unique for org/repo/branch. Set to override with custom naming the unique AWS resource identifier for the deployment. |
 | `aws_create_vpc` | bool | `false` | Whether an AWS VPC should be created in the action. Otherwise, the existing default VPC will be used. |
-| `infrastructure_only` | bool | `false` | Does infrastructure (i.e. terraform) but **not** the deployment (i.e. ansible) |
+| `infrastructure_only` | bool | `false` | Set to true to provision infrastructure (with Terraform) but skip the app deployment (with ansible) |
 | **Teraform configuration** |
 | `tf_state_bucket` | string | `${org}-${repo}-${branch}-tf-state` | AWS S3 bucket to use for Terraform state. By default, a new deployment will be created for each unique branch. Hardcode if you want to keep a shared resource state between the several branches. |
 | **StackStorm configuration** |

action.yaml

@@ -7,7 +7,7 @@ inputs:
   checkout:
     description: 'Specifies if this action should checkout the code'
     required: false
-    default: true
+    default: "true"
 
   # AWS Configuration
   aws_access_key_id:
@@ -29,13 +29,13 @@ inputs:
   aws_ec2_instance_profile:
     description: 'The AWS IAM instance profile to use for the EC2 instance. Use if you want to pass an AWS role with specific permissions granted to the instance'
   aws_resource_identifier:
-    description: 'Auto-generated by default so it's unique for org/repo/branch. Set to override with custom naming the unique AWS resource identifier for the deployment. Defaults to `${org}-${repo}-${branch}`.'
+    description: "Auto-generated by default so it's unique for org/repo/branch. Set to override with custom naming the unique AWS resource identifier for the deployment. Defaults to `${org}-${repo}-${branch}`."
   aws_create_vpc:
     description: 'Bool, whether an AWS VPC should be created in the action. Otherwise, the existing default VPC will be used.'
-    default: false
+    default: "false"
   infrastructure_only:
-    description: 'Does infrastructure (i.e. terraform) but **not** the deployment (i.e. ansible)'
-    default: false
+    description: 'Set to true to provision infrastructure (with Terraform) but skip the app deployment (with ansible)'
+    default: "false"
 
   # Terraform configuration
   tf_state_bucket:
@@ -56,10 +56,10 @@ inputs:
   # Cleanup
   tf_stack_destroy:
     description: 'Set to "true" to Destroy the created AWS infrastructure for this instance'
-    default: false
+    default: "false"
   tf_state_bucket_destroy:
     description: 'Force purge and deletion of tf_state_bucket defined. Any file contained there will be destroyed. tf_stack_destroy must also be true.'
-    default: false
+    default: "false"
 
 outputs:
   lb_url:
@@ -96,7 +96,7 @@ runs:
         # Skip ansible deployment if deploying only infrastructure
         ANSIBLE_SKIP_DEPLOY: ${{ inputs.infrastructure_only }}
 
-        BITOPS_FAST_FAIL: true
+        BITOPS_FAST_FAIL: "true"
 
         # ST2 config
         ST2_AUTH_USERNAME: ${{ inputs.st2_auth_username }}