GitHub action to deploy your application to Clever Cloud.
In your project's .clever.json, if the deploy_url value starts
with https://github.com/, your application is meant to be deployed
"from a Github repository" only.
If you try deploying it with this Github action, you will get the
following message in your logs: [ERROR] HTTP Error: 401 Authorization Required.
Currently (early 2023), the only workaround is to create a new application on Clever Cloud, that deploys "from a local repository", then remove the Clever Cloud webhook that has been created on your Github repository.
In your workflow file:
steps:
# This action requires an unshallow working copy,
# so the following prerequisites are necessary:
- uses: actions/checkout@v3
with:
fetch-depth: 0
# Deploy your application
- uses: 47ng/[email protected]
env:
CLEVER_TOKEN: ${{ secrets.CLEVER_TOKEN }}
CLEVER_SECRET: ${{ secrets.CLEVER_SECRET }}This minimal example assumes you have only one application for this
repository that was linked with clever link, and the .clever.json
file is versioned at the root of the repository. If that's not the case,
read on:
Clever Cloud uses a .clever.json file at the root of your repository
to link to application IDs.
If you have committed the .clever.json file, you only need to specify
the alias of the application to deploy:
- uses: 47ng/[email protected]
with:
alias: my-app-alias
env:
CLEVER_TOKEN: ${{ secrets.CLEVER_TOKEN }}
CLEVER_SECRET: ${{ secrets.CLEVER_SECRET }}If you don't have this .clever.json file or you want to explicly
deploy to another application, you can pass its ID:
- uses: 47ng/[email protected]
with:
appID: app_facade42-cafe-babe-cafe-deadf00dbaad
env:
CLEVER_TOKEN: ${{ secrets.CLEVER_TOKEN }}
CLEVER_SECRET: ${{ secrets.CLEVER_SECRET }}Application IDs can be found in the Clever Cloud console,
at the top-right corner of any page for a given app, or in the Information tab.
They look like app_{uuidv4}.
You will need to pass a token and a secret for authentication, via the
CLEVER_TOKEN and CLEVER_SECRET environment variables.
At the time of writing, the only way to obtain those credentials is to re-use the ones generated for a local CLI. For that:
- Install the
clever-toolsCLI locally - Login on the CLI with
clever loginand follow the Web login process - Extract the credentials:
$ cat ~/.config/clever-cloud/clever-tools.json
{"token":"[token]","secret":"[secret]"}- In your repository settings, add the following secrets:
CLEVER_TOKEN: thetokenvalue in the credentialsCLEVER_SECRET: thesecretvalue in the credentials
Support: introduced in v1.2.0
You can set extra environment variables on the deployed application under the
setEnv option. It follows the same syntax as .env files (newline-separated,
key=value).
- uses: 47ng/[email protected]
with:
setEnv: | # <- note the pipe here..
FOO=bar
EGG=spam
# ^-- ..and the indentation here
env:
CLEVER_TOKEN: ${{ secrets.CLEVER_TOKEN }}
CLEVER_SECRET: ${{ secrets.CLEVER_SECRET }}Note: you need to use a literal block scalar
|to preserve newlines in a YAML string.
Environment variables will be set before the application is deployed, to let the new deployment use them.
Multi-line environment variable values (eg: SSH keys, X.509 certificates) are currently not supported (due to splitting on newline), but contributions are welcome.
If the deployment fails, the environment variables will still have been updated. This could be a problem if your app restarts or scales up, as the new instance would use the new variable.
In the future, we might include a way to rollback environment variables set by this action if deployment fails.
Support: introduced in v1.2.0
Because build minutes are precious, and also because of two ongoing issues in the Clever Tools CLI ( #318, #319), you can specify a timeout in seconds after which the workflow will move on, regardless of the deployment status:
- uses: 47ng/[email protected]
with:
timeout: 1800 # wait at maximum 30 minutes before moving on
env:
CLEVER_TOKEN: ${{ secrets.CLEVER_TOKEN }}
CLEVER_SECRET: ${{ secrets.CLEVER_SECRET }}Support: introduced in v1.2.0
Clever Cloud uses a Git remote to perform deploys. By default, if the commit you want to deploy is not a fast-forward from the commit currently deployed, the deploy will be rejected. You can pass force: true to force the deploy anyway:
- uses: 47ng/[email protected]
with:
appID: app_facade42-cafe-babe-cafe-deadf00dbaad
force: true
env:
CLEVER_TOKEN: ${{ secrets.CLEVER_TOKEN }}
CLEVER_SECRET: ${{ secrets.CLEVER_SECRET }}Support: introduced in v1.3.1
You can write the deployment logs to a file for archiving:
- uses: 47ng/[email protected]
with:
logFile: ./clever-cloud-deploy.log
env:
CLEVER_TOKEN: ${{ secrets.CLEVER_TOKEN }}
CLEVER_SECRET: ${{ secrets.CLEVER_SECRET }}
# Optional: save the file as an artifact
- uses: actions/upload-artifact@v2
name: Upload deployment logs
with:
name: clever-cloud-deploy.log
path: ./clever-cloud-deploy.log
retention-days: 30If your deployment process is susceptible to log secrets or PII, you can also
disable it from printing onto the console, using the quiet option:
- uses: 47ng/[email protected]
with:
quiet: true
env:
CLEVER_TOKEN: ${{ secrets.CLEVER_TOKEN }}
CLEVER_SECRET: ${{ secrets.CLEVER_SECRET }}The action will detect the workflow commands
::notice, ::error, and ::warning being emitted from your deployment
logs, and will forward them so they can be used to annotate a run.
Note: this behaviour will be disabled if the quiet option is used.
This action follows SemVer.
To specify the version of the action to use:
uses: 47ng/[email protected]: latest stable versionuses: 47ng/actions-clever-cloud@3e5402496b8d6492401ebb3134acfeccc25c3fce: pinned to a specific Git SHA-1 (check out the releases)uses: docker://ghcr.io/47ng/actions-clever-cloud:latest: latest code from master (not recommended, as it may break: hic sunt dracones.)
Note:
uses: 47ng/actions-clever-cloud@masterwill not use the latest code on themasterbranch, because the action manifest is pinned on the latest relase for performance reasons (it saves rebuilding the Docker image when consuming the action).If you wish to test unreleased features, go through Docker directly.
Note: as of 2023-03-24, Docker images have been copied from Docker Hub (
47ng/actions-clever-cloud) to GitHub Container Registry (ghcr.io/47ng/actions-clever-cloud), in response to Docker's plan to delete open source organisations on free plans.Although they backtracked on this decision, the images are now dual-published on both platforms, and default to being downloaded from GitHub Container Registry for (seemingly) better performance.
Clever Cloud lets you connect your GitHub repository so that any push is deployed. This is great for staging environments, but in some cases you may want to deploy to production only on specific events, like a release being published, or after a CI run.
MIT - Made with ❤️ by François Best
Using this action at work ? Sponsor me to help with support and maintenance.
![dependabot-preview[bot] avatar](https://avatars.githubusercontent.com/in/2141?v=4 "dependabot-preview[bot]")
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot]")
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent