Skip to content
Snippets Groups Projects
Commit 6b6b756d authored by Marlon Moser's avatar Marlon Moser
Browse files

docs: apply suggestions

parent b36e33b0
Branches
Tags
No related merge requests found
...@@ -578,12 +578,12 @@ See also the official GitLab documentation for it ...@@ -578,12 +578,12 @@ See also the official GitLab documentation for it
If you want to save runner resources you may disable the unit and integration tests If you want to save runner resources you may disable the unit and integration tests
by setting the `SKIP_TESTS` CI/CD variable to `true`. by setting the `SKIP_TESTS` CI/CD variable to `true`.
The Component builds by default a multi-arch image for `linux/amd64` and `linux/arm64`. The component builds by default a multi-arch image for `linux/amd64` and `linux/arm64`.
There are multiple reasons why you might want to change this behavior, like saving runner resources. There are multiple reasons why you might want to change this behavior, like saving runner resources.
To configure for what architectures the container image should be built, you can go to To configure for what architectures the container image should be built, you can go to
the CI/CD variables in the project settings and add a variable called `PLATFORMS`. the CI/CD variables in the project settings and add a variable called `PLATFORMS`.
The value is one or more `OS/ARCH[/VARIANT]`. If you have multiple platforms, they have to be comma separated. The value is one or more `OS/ARCH[/VARIANT]`. If you have multiple platforms, they have to be comma separated.
**Keep in mind that the component is tested with linux/amd64 and linux/arm64, **Keep in mind that the component is tested with `linux/amd64` and `linux/arm64`,
other platforms are not officially supported!** other platforms are not officially supported!**
You can set the `OPENTOFU_COMPONENT_IMAGE_BUILD_RUNNER_TAG` CI/CD variable to a custom runner tag You can set the `OPENTOFU_COMPONENT_IMAGE_BUILD_RUNNER_TAG` CI/CD variable to a custom runner tag
......
...@@ -654,12 +654,12 @@ See also the official GitLab documentation for it ...@@ -654,12 +654,12 @@ See also the official GitLab documentation for it
If you want to save runner resources you may disable the unit and integration tests If you want to save runner resources you may disable the unit and integration tests
by setting the `SKIP_TESTS` CI/CD variable to `true`. by setting the `SKIP_TESTS` CI/CD variable to `true`.
The Component builds by default a multi-arch image for `linux/amd64` and `linux/arm64`. The component builds by default a multi-arch image for `linux/amd64` and `linux/arm64`.
There are multiple reasons why you might want to change this behavior, like saving runner resources. There are multiple reasons why you might want to change this behavior, like saving runner resources.
To configure for what architectures the container image should be built, you can go to To configure for what architectures the container image should be built, you can go to
the CI/CD variables in the project settings and add a variable called `PLATFORMS`. the CI/CD variables in the project settings and add a variable called `PLATFORMS`.
The value is one or more `OS/ARCH[/VARIANT]`. If you have multiple platforms, they have to be comma separated. The value is one or more `OS/ARCH[/VARIANT]`. If you have multiple platforms, they have to be comma separated.
**Keep in mind that the component is tested with linux/amd64 and linux/arm64, **Keep in mind that the component is tested with `linux/amd64` and `linux/arm64`,
other platforms are not officially supported!** other platforms are not officially supported!**
You can set the `OPENTOFU_COMPONENT_IMAGE_BUILD_RUNNER_TAG` CI/CD variable to a custom runner tag You can set the `OPENTOFU_COMPONENT_IMAGE_BUILD_RUNNER_TAG` CI/CD variable to a custom runner tag
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment