Merge pull request #6 from Escape-Technologies/fix/documentation

fix: update options documentation

README.md

@@ -28,7 +28,9 @@ You can find theses values in your Escape application settings.
 - `configuration_override_path`: Loads `configuration_override` from a file. [See the docs on configuration overrides](https://escape.tech/docs/ci-cd/techniques/configuration-override)
 - `introspection_file`: The relative path to a JSON file containing an introspection response for updating the application's introspection on Escape. [See the docs on introspection update](https://docs.escape.tech/ci-cd/introspection-update)
 - `schema_file`: The relative path to a GraphQL schema file for updating the application's introspection on Escape. [See the docs on introspection update](https://docs.escape.tech/ci-cd/introspection-update)
+- `schema_url`: The url to a GraphQL schema file for updating the application's introspection on Escape. [See the docs on introspection update](https://docs.escape.tech/ci-cd/introspection-update)
 - `fail_on_severities`: A csv-delimited list of severities to fail on, can be HIGH, MEDIUM, LOW, INFO. [See the docs from the cli](https://www.npmjs.com/package/@escape.tech/action)
+- `fail_on_compliance`: A JSON string to define exact controls in an array (or all of them with *), per compliance framework supported. [See the docs from the cli](https://www.npmjs.com/package/@escape.tech/action)
 
 ## Usage example
 

action.yml

@@ -38,8 +38,10 @@ runs:
     CONFIGURATION_OVERRIDE: ${{ inputs.configuration_override }}
     CONFIGURATION_OVERRIDE_PATH: ${{ inputs.configuration_override_path }}
     SCHEMA_FILE: ${{ inputs.schema_file }}
+    SCHEMA_URL: ${{ inputs.schema_url }}
     INTROSPECTION_FILE: ${{ inputs.introspection_file }}
     FAIL_ON_SEVERITIES: ${{ inputs.fail_on_severities }}
+    FAIL_ON_COMPLIANCE: ${{ inputs.fail_on_compliance }}
 
 branding:
   icon: "check"