public-mirrors/werf-actions
2
0
Fork 0
mirror of https://github.com/werf/actions.git synced 2026-02-05 10:56:23 +03:00
Code Issues Packages Projects Releases Wiki Activity

[readme] Move to werf organization

Browse Source
This commit is contained in:
Alexey Igrychev
2020-06-05 14:33:39 +01:00
parent d50c87dc2a
commit d7370d10e7
11 changed files with 87 additions and 88 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
converge/README.md
View File

@@ -1,5 +1,5 @@
<p align="center">
<img src="https://github.com/flant/werf/raw/master/docs/images/werf-logo.svg?sanitize=true" style="max-height:100%;" height="175">
<img src="https://github.com/werf/werf/raw/master/docs/images/werf-logo.svg?sanitize=true" style="max-height:100%;" height="175">
</p>
___
@@ -9,13 +9,13 @@ The action combines all the necessary steps in itself and logic may be divided i
### werf binary setup
By default, all actions setup actual werf version for [1.1 alpha channel](https://werf.io/releases.html) (more details about channels, werf release cycle and compatibility promise [here](https://github.com/flant/werf#backward-compatibility-promise)).
By default, all actions setup actual werf version for [1.1 alpha channel](https://werf.io/releases.html) (more details about channels, werf release cycle and compatibility promise [here](https://github.com/werf/werf#backward-compatibility-promise)).
Using `group` and `channel` inputs the user can switch the release channel.
> This is recommended approach to be up-to-date and to use actual werf version without changing configurations
```yaml
- uses: flant/werf-actions/converge@master
- uses: werf/actions/converge@master
with:
group: 1.1
channel: alpha
@@ -24,7 +24,7 @@ Using `group` and `channel` inputs the user can switch the release channel.
Withal, it is not necessary to work within release channels, and the user might specify certain werf version with `version` input.
```yaml
- uses: flant/werf-actions/converge@master
- uses: werf/actions/converge@master
with:
version: v1.1.16
```
@@ -38,7 +38,7 @@ The _kubeconfig_ may be used for deployment, cleanup, distributed locks and cach
* Pass secret with `kube-config-base64-data` input:
```yaml
- uses: flant/werf-actions/converge@master
- uses: werf/actions/converge@master
with:
kube-config-base64-data: ${{ secrets.KUBE_CONFIG_BASE64_DATA }}
```
@@ -56,7 +56,7 @@ By default, action will use the token provided to your workflow.
Any werf option can be defined with environment variables:
```yaml
- uses: flant/werf-actions/converge@master
- uses: werf/actions/converge@master
with:
env: production
env:
@@ -103,7 +103,7 @@ converge:
fetch-depth: 0
- name: Converge
uses: flant/werf-actions/converge@master
uses: werf/actions/converge@master
with:
kube-config-base64-data: ${{ secrets.KUBE_CONFIG_BASE64_DATA }}
env: production