ArvanCloud PaaS Action
ActionsTags
(1)
With this action you can update your deployment on ArvanCloud PaaS/CaaS.
- name: R1C Action
uses: hatamiarash7/[email protected]
with:
region: 1
auth: ${{ secrets.API_TOKEN }}
app: my-application
container: proxy
image: nginx:1.23.1-alpineYou can use the
debugbranch to see more logs. It'shatamiarash7/ar-paas-action@debug.
Following inputs can be used as with keys
| Name | Type | Default | Description |
|---|---|---|---|
region |
1 |
Your Arvancloud Region | |
auth |
Required | Your API token | |
namespace |
The target namespace ( project ). Will be the default project if not specified | ||
app |
Required | Application's name in your PaaS project | |
container |
Required | The container that you want to update its image | |
image |
Required | Docker image like org/image:tag |
|
version |
1.3.6 |
Version of ArvanCloud CLI tool |
We have 2 regions in ArvanCloud PaaS/CaaS for now:
1forir-thr-ba1( Openshift )2forir-thr-ba2( Kubernetes )
You should get your API key from ArvanCloud Dashboard > Settings > API keys. You need a key with Container Service permission.
Define this key as a Repository/Organization secret.
Check ArvanCloud Documentation for more information.
Don't be shy and reach out to us if you want to contribute.
- Fork it !
- Create your feature branch :
git checkout -b my-new-feature - Commit your changes :
git commit -am 'Add some feature' - Push to the branch :
git push origin my-new-feature - Submit a pull request
Each project may have many problems. Contributing to the better development of this project by reporting them.
ArvanCloud PaaS Action is not certified by GitHub. It is provided by a third-party and is governed by separate terms of service, privacy policy, and support documentation.
Tags
(1)ArvanCloud PaaS Action is not certified by GitHub. It is provided by a third-party and is governed by separate terms of service, privacy policy, and support documentation.