From ca52a4e8ec26159a51e5f0ac5c9c4cf8da0a1c3b Mon Sep 17 00:00:00 2001 From: Alexey Igrychev Date: Wed, 10 Mar 2021 14:37:41 +0000 Subject: [PATCH 1/2] [readme] Update channels, werf release cycle and compatibility promise link --- README.md | 2 +- build/README.md | 2 +- cleanup/README.md | 2 +- converge/README.md | 2 +- dismiss/README.md | 2 +- install/README.md | 2 +- run/README.md | 2 +- 7 files changed, 7 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index b0087c8..c03cdaa 100644 --- a/README.md +++ b/README.md @@ -21,7 +21,7 @@ Each action combines all the necessary steps in itself and logic may be divided ### werf binary setup -By default, all actions setup actual werf version for [1.2 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)). +By default, all actions setup actual werf version for [1.2 alpha channel](https://werf.io/releases.html) (more details about channels, werf release cycle and compatibility promise [here](https://werf.io/installation.html#all-changes-in-werf-go-through-all-stability-channels)). 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 diff --git a/build/README.md b/build/README.md index db77eca..89c6a92 100644 --- a/build/README.md +++ b/build/README.md @@ -9,7 +9,7 @@ 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.2 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)). +By default, all actions setup actual werf version for [1.2 alpha channel](https://werf.io/releases.html) (more details about channels, werf release cycle and compatibility promise [here](https://werf.io/installation.html#all-changes-in-werf-go-through-all-stability-channels)). 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 diff --git a/cleanup/README.md b/cleanup/README.md index 216df01..1131982 100644 --- a/cleanup/README.md +++ b/cleanup/README.md @@ -9,7 +9,7 @@ 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.2 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)). +By default, all actions setup actual werf version for [1.2 alpha channel](https://werf.io/releases.html) (more details about channels, werf release cycle and compatibility promise [here](https://werf.io/installation.html#all-changes-in-werf-go-through-all-stability-channels)). 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 diff --git a/converge/README.md b/converge/README.md index 2a3e14d..10aca43 100644 --- a/converge/README.md +++ b/converge/README.md @@ -9,7 +9,7 @@ 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.2 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)). +By default, all actions setup actual werf version for [1.2 alpha channel](https://werf.io/releases.html) (more details about channels, werf release cycle and compatibility promise [here](https://werf.io/installation.html#all-changes-in-werf-go-through-all-stability-channels)). 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 diff --git a/dismiss/README.md b/dismiss/README.md index 5d6b90e..d40c70c 100644 --- a/dismiss/README.md +++ b/dismiss/README.md @@ -9,7 +9,7 @@ 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.2 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)). +By default, all actions setup actual werf version for [1.2 alpha channel](https://werf.io/releases.html) (more details about channels, werf release cycle and compatibility promise [here](https://werf.io/installation.html#all-changes-in-werf-go-through-all-stability-channels)). 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 diff --git a/install/README.md b/install/README.md index 796fa31..03bb7e1 100644 --- a/install/README.md +++ b/install/README.md @@ -3,7 +3,7 @@

___ -By default, all actions setup actual werf version for [1.2 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)). +By default, all actions setup actual werf version for [1.2 alpha channel](https://werf.io/releases.html) (more details about channels, werf release cycle and compatibility promise [here](https://werf.io/installation.html#all-changes-in-werf-go-through-all-stability-channels)). 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 diff --git a/run/README.md b/run/README.md index efc515f..3ddae6b 100644 --- a/run/README.md +++ b/run/README.md @@ -9,7 +9,7 @@ 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.2 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)). +By default, all actions setup actual werf version for [1.2 alpha channel](https://werf.io/releases.html) (more details about channels, werf release cycle and compatibility promise [here](https://werf.io/installation.html#all-changes-in-werf-go-through-all-stability-channels)). 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 From d8c14de78e8c47f68a45b0b560636f19832d1263 Mon Sep 17 00:00:00 2001 From: Alexey Igrychev Date: Wed, 10 Mar 2021 14:53:46 +0000 Subject: [PATCH 2/2] [readme] Add "Working with container registry" section --- README.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/README.md b/README.md index c03cdaa..eb3e5ae 100644 --- a/README.md +++ b/README.md @@ -72,6 +72,21 @@ Any werf option can be defined with environment variables: WERF_LOG_VERBOSE: "on" ``` +## Working with container registry + +Due to the fact that the new GitHub container registry (`ghcr.io`) does not currently support removal, all actions default to the old one (`docker.pkg.github.com`). + +If necessary, the user can define an arbitrary container registry using the `WERF_REPO` and `WERF_REPO_CONTAINER_REGISTRY` environment variables. + +```yaml +- uses: werf/actions/converge@v1.2 + env: + WERF_REPO: "gcr.io/company/app" + WERF_REPO_CONTAINER_REGISTRY: "gcr" +``` + +To learn how to work with the different container registries, see the corresponding [article in the werf documentation](https://werf.io/documentation/advanced/supported_container_registries.html). + ## Examples ### converge