address PR comments: prettify consistently, require all inputs, impro…

…ve README, add missing types for vultr-node, rebuild dist

accept operating system input by name (os_type) rather than Vultr ID

README.md

@@ -1,9 +1,15 @@
 # vultr-action
 
-This script creates and destroys pizzas on Vultr - that is, an instance and associated DNS records.
-
-It uses a dedicated node client called [vultr-node](https://github.com/vultr/vultr-node) to interact with the Vultr API.
+This Github Action creates and destroys instances, and associated DNS records, on the Vultr cloud service.
 
 ## v2
 
-Teardown should now work on DNS records!
+The latest major version of this action uses a dedicated node client called [vultr-node](https://github.com/vultr/vultr-node) to interact with the Vultr API.
+
+It includes a fix to the teardown of DNS records, which was previously unreliable.
+
+There are some breaking changes in terms of the inputs required (e.g. improved naming consistency, operating system submitted by name rather than ID).
+
+### operating systems
+
+A constant defining the operating systems currently supported by this action can be found in `src/common.ts`. You can get a full list of Vultr OS options from the CLI with the command `vultr-cli os list`. Please open a PR if you want to use this action to spin up an OS not included there.

action.yml

@@ -6,11 +6,17 @@ inputs:
   api_key:
     required: true
   domain:
-    required: false
-  os:
-    required: false
+    required: true
+  os_type:
+    required: true
+  plan:
+    required: true
   pull_request_id:
     required: true
+  region:
+    required: true
+  tag:
+    required: true
 outputs:
   ip_address:
     description: "IP address"