mirror of
https://github.com/cloudflare/wrangler-action.git
synced 2024-10-06 20:43:25 +02:00
9e7e2ec6db
- 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
21 lines
783 B
YAML
21 lines
783 B
YAML
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"
|