From 448f6c68d8e02696cf06223973816e5d9e727bf5 Mon Sep 17 00:00:00 2001 From: Alexey Igrychev Date: Thu, 28 May 2020 07:18:25 +0100 Subject: [PATCH] [readme] @v1 -> @master --- README.md | 16 ++++++++-------- build-and-publish/README.md | 10 +++++----- cleanup/README.md | 10 +++++----- converge/README.md | 10 +++++----- deploy/README.md | 10 +++++----- dismiss/README.md | 10 +++++----- install/README.md | 8 ++++---- 7 files changed, 37 insertions(+), 37 deletions(-) diff --git a/README.md b/README.md index 87ca523..b9cf54b 100644 --- a/README.md +++ b/README.md @@ -25,7 +25,7 @@ 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@v1 +- uses: flant/werf-actions/converge@master with: group: 1.1 channel: alpha @@ -34,7 +34,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@v1 +- uses: flant/werf-actions/converge@master with: version: v1.1.16 ``` @@ -48,7 +48,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/build-and-publish@v1 + - uses: flant/werf-actions/build-and-publish@master with: kube-config-base64-data: ${{ secrets.KUBE_CONFIG_BASE64_DATA }} ``` @@ -66,7 +66,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/build-and-publish@v1 +- uses: flant/werf-actions/build-and-publish@master env: WERF_LOG_VERBOSE: "on" WERF_TAG_CUSTOM_TAG1: tag1 @@ -143,7 +143,7 @@ dismiss: uses: actions/checkout@v2 - name: Dismiss - uses: flant/werf-actions/dismiss@v1 + uses: flant/werf-actions/dismiss@master with: kube-config-base64-data: ${{ secrets.KUBE_CONFIG_BASE64_DATA }} env: production @@ -164,7 +164,7 @@ cleanup: run: git fetch --prune --unshallow - name: Cleanup - uses: flant/werf-actions/cleanup@v1 + uses: flant/werf-actions/cleanup@master with: kube-config-base64-data: ${{ secrets.KUBE_CONFIG_BASE64_DATA }} ``` @@ -178,10 +178,10 @@ werf: steps: - name: Checkout code - uses: actions/checkout@v1 + uses: actions/checkout@master - name: Install werf CLI - uses: flant/werf-actions/install@v1 + uses: flant/werf-actions/install@master # for deploy and distributed locks - name: Create kube config diff --git a/build-and-publish/README.md b/build-and-publish/README.md index f6dc2c2..3297082 100644 --- a/build-and-publish/README.md +++ b/build-and-publish/README.md @@ -15,7 +15,7 @@ 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/build-and-publish@v1 +- uses: flant/werf-actions/build-and-publish@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/build-and-publish@v1 +- uses: flant/werf-actions/build-and-publish@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/build-and-publish@v1 + - uses: flant/werf-actions/build-and-publish@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/build-and-publish@v1 +- uses: flant/werf-actions/build-and-publish@master env: WERF_LOG_VERBOSE: "on" WERF_TAG_CUSTOM_TAG1: tag1 @@ -100,7 +100,7 @@ build-and-publish: fetch-depth: 0 - name: Build and Publish - uses: flant/werf-actions/build-and-publish@v1 + uses: flant/werf-actions/build-and-publish@master with: kube-config-base64-data: ${{ secrets.KUBE_CONFIG_BASE64_DATA }} ``` diff --git a/cleanup/README.md b/cleanup/README.md index 5e94a6f..3860023 100644 --- a/cleanup/README.md +++ b/cleanup/README.md @@ -15,7 +15,7 @@ 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/cleanup@v1 +- uses: flant/werf-actions/cleanup@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/cleanup@v1 +- uses: flant/werf-actions/cleanup@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/cleanup@v1 + - uses: flant/werf-actions/cleanup@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/cleanup@v1 +- uses: flant/werf-actions/cleanup@master env: WERF_LOG_VERBOSE: "on" ``` @@ -99,7 +99,7 @@ cleanup: run: git fetch --prune --unshallow - name: Cleanup - uses: flant/werf-actions/cleanup@v1 + uses: flant/werf-actions/cleanup@master with: kube-config-base64-data: ${{ secrets.KUBE_CONFIG_BASE64_DATA }} ``` diff --git a/converge/README.md b/converge/README.md index 0ac4661..4e53e23 100644 --- a/converge/README.md +++ b/converge/README.md @@ -15,7 +15,7 @@ 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@v1 +- uses: flant/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@v1 +- uses: flant/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@v1 + - uses: flant/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@v1 +- uses: flant/werf-actions/converge@master with: env: production env: @@ -103,7 +103,7 @@ converge: fetch-depth: 0 - name: Converge - uses: flant/werf-actions/converge@v1 + uses: flant/werf-actions/converge@master with: kube-config-base64-data: ${{ secrets.KUBE_CONFIG_BASE64_DATA }} env: production diff --git a/deploy/README.md b/deploy/README.md index 2d3b664..09943f5 100644 --- a/deploy/README.md +++ b/deploy/README.md @@ -15,7 +15,7 @@ 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/deploy@v1 +- uses: flant/werf-actions/deploy@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/deploy@v1 +- uses: flant/werf-actions/deploy@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/deploy@v1 + - uses: flant/werf-actions/deploy@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/deploy@v1 +- uses: flant/werf-actions/deploy@master with: env: production env: @@ -103,7 +103,7 @@ deploy: fetch-depth: 0 - name: Deploy - uses: flant/werf-actions/deploy@v1 + uses: flant/werf-actions/deploy@master with: kube-config-base64-data: ${{ secrets.KUBE_CONFIG_BASE64_DATA }} env: production diff --git a/dismiss/README.md b/dismiss/README.md index 8887938..921a622 100644 --- a/dismiss/README.md +++ b/dismiss/README.md @@ -15,7 +15,7 @@ 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@v1 +- uses: flant/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@v1 +- uses: flant/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@v1 + - uses: flant/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@v1 +- uses: flant/werf-actions/converge@master with: env: production env: @@ -101,7 +101,7 @@ dismiss: uses: actions/checkout@v2 - name: Dismiss - uses: flant/werf-actions/dismiss@v1 + uses: flant/werf-actions/dismiss@master with: kube-config-base64-data: ${{ secrets.KUBE_CONFIG_BASE64_DATA }} env: production diff --git a/install/README.md b/install/README.md index fd402af..281a7ab 100644 --- a/install/README.md +++ b/install/README.md @@ -9,7 +9,7 @@ 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/install@v1 +- uses: flant/werf-actions/install@master with: group: 1.1 channel: alpha @@ -18,7 +18,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/install@v1 +- uses: flant/werf-actions/install@master with: version: v1.1.16 ``` @@ -48,10 +48,10 @@ werf: steps: - name: Checkout code - uses: actions/checkout@v1 + uses: actions/checkout@master - name: Install werf CLI - uses: flant/werf-actions/install@v1 + uses: flant/werf-actions/install@master # for deploy and distributed locks - name: Create kube config