Add service-managed-ebs-volume and run-task-managed-ebs-volume inputs to the action.yml file

Author: amazreech

action.yml

@@ -40,6 +40,15 @@ inputs:
   force-new-deployment:
     description: 'Whether to force a new deployment of the service. Valid value is "true". Will default to not force a new deployment.'
     required: false
+  service-managed-ebs-volume-name:
+    description: "The name of the volume to manage in the ECS service."
+    required: false
+  service-managed-ebs-volume:
+    description: "A JSON object that defines the configuration for the Amazon EBS volume that Amazon ECS creates and 
+                  manages on your behalf. These settings are used to create each Amazon EBS volume, with one volume created for 
+                  each task in the service. The Amazon EBS volumes are visible in your account in the Amazon EC2 console once they 
+                  are created."
+    required: false
   run-task:
     description: 'A boolean indicating whether to run a stand-alone task in a ECS cluster. Task will run before the service is updated if both are provided. Default value is false .'
     required: false
@@ -67,6 +76,15 @@ inputs:
   run-task-tags:
     description: 'A JSON array of tags.'
     required: false
+  run-task-managed-ebs-volume-name:
+    description: "The name of the volume to manage in the ECS service."
+    required: false
+  run-task-managed-ebs-volume:
+    description: "A JSON object that defines the configuration for the Amazon EBS volume that Amazon ECS creates and 
+                  manages on your behalf. These settings are used to create each Amazon EBS volume, with one volume created for 
+                  each task in the service. The Amazon EBS volumes are visible in your account in the Amazon EC2 console once they 
+                  are created."
+    required: false
   wait-for-task-stopped:
     description: 'Whether to wait for the task to stop when running it outside of a service. Will default to not wait.'
     required: false