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

Actions for v1.2 werf version

Browse Source 
- remove actions not used in v1.2
- update the example arbitrary version
- embed v1.2 MAJOR.MINOR
This commit is contained in:
Alexey Igrychev
2021-03-10 14:06:15 +00:00
parent f933394504
commit 2df7b68580
27 changed files with 64 additions and 134152 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
cleanup/README.md
View File

@@ -15,7 +15,7 @@ Using the `channel` input 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: werf/actions/cleanup@v1.1
- uses: werf/actions/cleanup@v1.2
with:
channel: alpha
```
@@ -23,9 +23,9 @@ Using the `channel` input 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: werf/actions/cleanup@v1.1
- uses: werf/actions/cleanup@v1.2
with:
version: v1.1.23
version: v1.2.9
```
### kubeconfig setup (*optional*)
@@ -37,7 +37,7 @@ The _kubeconfig_ may be used for deployment, cleanup, distributed locks and cach
* Pass secret with `kube-config-base64-data` input:
```yaml
- uses: werf/actions/cleanup@v1.1
- uses: werf/actions/cleanup@v1.2
with:
kube-config-base64-data: ${{ secrets.KUBE_CONFIG_BASE64_DATA }}
```
@@ -55,7 +55,7 @@ By default, action will use the token provided to your workflow.
Any werf option can be defined with environment variables:
```yaml
- uses: werf/actions/cleanup@v1.1
- uses: werf/actions/cleanup@v1.2
env:
WERF_LOG_VERBOSE: "on"
```
@@ -94,7 +94,7 @@ cleanup:
run: git fetch --prune --unshallow
- name: Cleanup
uses: werf/actions/cleanup@v1.1
uses: werf/actions/cleanup@v1.2
with:
kube-config-base64-data: ${{ secrets.KUBE_CONFIG_BASE64_DATA }}
```