wrangler-action/action.yml

name: "Deploy to Cloudflare Workers with Wrangler"
branding:
  icon: "upload-cloud"
  color: "orange"
description: "Deploy your Cloudflare Workers applications and sites directly from GitHub, using Wrangler"
runs:
  using: "docker"
  image: "Dockerfile"
inputs:
  apiKey:
    description: "(Legacy) Your Cloudflare API Key"
  apiToken:
    description: "Your Cloudflare API Token"
  email:
    description: "(Legacy) Your Cloudflare Email"
  environment:
    description: "The environment you'd like to publish your Workers project to - must be defined in wrangler.toml"
  workingDirectory:
    description: "The relative path which Wrangler commands should be run from"
  wranglerVersion:
    description: "The version of Wrangler you'd like to use to publish your Workers project"
  secrets:
    description: "A new line deliminated string of environment variable names that should be configured as Worker secrets"
    required: false
  preCommands:
    description: "Commands to execute before publishing the Workers project"
    required: false
  postCommands:
    description: "Commands to execute after publishing the Workers project"
    required: false
  publish:
    description: "Set to false to skip publishing your Worker project and secrets.  Defaults to true."
    required: false
add secrets publishing 2020-06-16 06:09:55 +02:00			`name: "Deploy to Cloudflare Workers with Wrangler"`
Add icon and color 2019-10-15 17:14:20 +02:00			`branding:`
add secrets publishing 2020-06-16 06:09:55 +02:00			`icon: "upload-cloud"`
			`color: "orange"`
			`description: "Deploy your Cloudflare Workers applications and sites directly from GitHub, using Wrangler"`
Initial commit 2019-10-07 21:41:21 +02:00			`runs:`
add secrets publishing 2020-06-16 06:09:55 +02:00			`using: "docker"`
			`image: "Dockerfile"`
Switch to inputs 2019-10-11 21:25:47 +02:00			`inputs:`
Add environment support, change input names 2019-10-14 22:24:54 +02:00			`apiKey:`
It's wrangler-action 1.1.0! 📡 - Support `apiToken` as an authentication method - Deprecates `apiKey` and `email`, making them optional parameters and encouraging `apiToken` usage in build logs - Support `wranglerVersion` for installing a specific Wrangler version for your build - Per #7, support for `workingDirectory` to run `wrangler-action` in a specific directory in your repo - Adds a test Workers project under the `test` directory. This is used in the repo's new set of workflows (see below) - Adds a GitHub Action workflow that: - Lints `entrypoint.sh` to ensure that the shell script looks correct - Runs the action with various config options to ensure future pushes don't introduce regressions 2019-11-22 17:27:40 +01:00			`description: "(Legacy) Your Cloudflare API Key"`
			`apiToken:`
			`description: "Your Cloudflare API Token"`
Add environment support, change input names 2019-10-14 22:24:54 +02:00			`email:`
It's wrangler-action 1.1.0! 📡 - Support `apiToken` as an authentication method - Deprecates `apiKey` and `email`, making them optional parameters and encouraging `apiToken` usage in build logs - Support `wranglerVersion` for installing a specific Wrangler version for your build - Per #7, support for `workingDirectory` to run `wrangler-action` in a specific directory in your repo - Adds a test Workers project under the `test` directory. This is used in the repo's new set of workflows (see below) - Adds a GitHub Action workflow that: - Lints `entrypoint.sh` to ensure that the shell script looks correct - Runs the action with various config options to ensure future pushes don't introduce regressions 2019-11-22 17:27:40 +01:00			`description: "(Legacy) Your Cloudflare Email"`
Add environment support, change input names 2019-10-14 22:24:54 +02:00			`environment:`
			`description: "The environment you'd like to publish your Workers project to - must be defined in wrangler.toml"`
Add workingDirectory option for publishing a subdirectory 2019-11-07 22:15:49 +01:00			`workingDirectory:`
			`description: "The relative path which Wrangler commands should be run from"`
It's wrangler-action 1.1.0! 📡 - Support `apiToken` as an authentication method - Deprecates `apiKey` and `email`, making them optional parameters and encouraging `apiToken` usage in build logs - Support `wranglerVersion` for installing a specific Wrangler version for your build - Per #7, support for `workingDirectory` to run `wrangler-action` in a specific directory in your repo - Adds a test Workers project under the `test` directory. This is used in the repo's new set of workflows (see below) - Adds a GitHub Action workflow that: - Lints `entrypoint.sh` to ensure that the shell script looks correct - Runs the action with various config options to ensure future pushes don't introduce regressions 2019-11-22 17:27:40 +01:00			`wranglerVersion:`
			`description: "The version of Wrangler you'd like to use to publish your Workers project"`
add secrets publishing 2020-06-16 06:09:55 +02:00			`secrets:`
			`description: "A new line deliminated string of environment variable names that should be configured as Worker secrets"`
			`required: false`
pre-post-commands 2020-08-07 23:16:42 +02:00			`preCommands:`
			`description: "Commands to execute before publishing the Workers project"`
			`required: false`
			`postCommands:`
			`description: "Commands to execute after publishing the Workers project"`
			`required: false`
add ability to skip publish 2020-08-12 05:46:42 +02:00			`publish:`
			`description: "Set to false to skip publishing your Worker project and secrets. Defaults to true."`
			`required: false`