Skip to content
Snippets Groups Projects
Commit 0beff3d6 authored by Timo Furrer's avatar Timo Furrer
Browse files

Merge branch 'use-on-self-managed' into 'main'

Document usage on self-managed

See merge request components/opentofu!27
parents 9d1bffd4 cfbd6769
No related branches found
No related tags found
No related merge requests found
...@@ -149,6 +149,27 @@ However, we cannot use the alternative `+` which would indicate build metadata ...@@ -149,6 +149,27 @@ However, we cannot use the alternative `+` which would indicate build metadata
as we'd like. as we'd like.
See https://github.com/distribution/distribution/issues/1201* See https://github.com/distribution/distribution/issues/1201*
## Usage on self-managed
GitLab CI/CD components are not yet distributed and available on self-managed GitLab instances.
(see details [here](https://gitlab.com/gitlab-org/gitlab/-/issues/415638)).
It's also not possible to just include CI/CD components across instance, thus an include like
`- component: gitlab.com/components/opentofu/full-pipeline@~latest` won't work from a
self-managed instance.
However, you could mirror this project from GitLab.com onto any self-managed instance using
a [repository pull mirror](https://docs.gitlab.com/ee/user/project/repository/mirror/pull.html).
and then use the component as you would from GitLab.com, but change the domain, like so:
```yaml
include:
- component: gitlab.example.com/components/opentofu/full-pipeline@~latest
inputs:
...
```
This example assumes your GitLab instance is hosted on `gitlab.example.com` and this component
project is mirrored in the `components/opentofu` project.
## Contributing ## Contributing
See the [CONTRIBUTING.md](CONTRIBUTING.md) guide. See the [CONTRIBUTING.md](CONTRIBUTING.md) guide.
...@@ -168,6 +168,27 @@ However, we cannot use the alternative `+` which would indicate build metadata ...@@ -168,6 +168,27 @@ However, we cannot use the alternative `+` which would indicate build metadata
as we'd like. as we'd like.
See https://github.com/distribution/distribution/issues/1201* See https://github.com/distribution/distribution/issues/1201*
## Usage on self-managed
GitLab CI/CD components are not yet distributed and available on self-managed GitLab instances.
(see details [here](https://gitlab.com/gitlab-org/gitlab/-/issues/415638)).
It's also not possible to just include CI/CD components across instance, thus an include like
`- component: gitlab.com/components/opentofu/full-pipeline@~latest` won't work from a
self-managed instance.
However, you could mirror this project from GitLab.com onto any self-managed instance using
a [repository pull mirror](https://docs.gitlab.com/ee/user/project/repository/mirror/pull.html).
and then use the component as you would from GitLab.com, but change the domain, like so:
```yaml
include:
- component: gitlab.example.com/components/opentofu/full-pipeline@~latest
inputs:
...
```
This example assumes your GitLab instance is hosted on `gitlab.example.com` and this component
project is mirrored in the `components/opentofu` project.
## Contributing ## Contributing
See the [CONTRIBUTING.md](CONTRIBUTING.md) guide. See the [CONTRIBUTING.md](CONTRIBUTING.md) guide.
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment