**Note:**`filename` is deprecated in favor of `path`. Both return the full path of the file inside the repository, but in the future `filename` will be only the file name and not the full path (see [this issue][gitlab-34521]).
### Scope: commits **(STARTER)**
This scope is available only if [Elasticsearch](../integration/elasticsearch.md) is enabled.
...
...
@@ -367,6 +370,7 @@ Example response:
{
"basename":"README",
"data":"```\n\n## Installation\n\nQuick start using the [pre-built",
"path":"README.md",
"filename":"README.md",
"id":null,
"ref":"master",
...
...
@@ -376,6 +380,8 @@ Example response:
]
```
**Note:**`filename` is deprecated in favor of `path`. Both return the full path of the file inside the repository, but in the future `filename` will be only the file name and not the full path (see [this issue][gitlab-34521]).
### Scope: users
```bash
...
...
@@ -633,6 +639,7 @@ Example response:
{
"basename":"home",
"data":"hello\n\nand bye\n\nend",
"path":"home.md",
"filename":"home.md",
"id":null,
"ref":"master",
...
...
@@ -642,6 +649,8 @@ Example response:
]
```
**Note:**`filename` is deprecated in favor of `path`. Both return the full path of the file inside the repository, but in the future `filename` will be only the file name and not the full path (see [this issue][gitlab-34521]).
### Scope: commits **(STARTER)**
This scope is available only if [Elasticsearch](../integration/elasticsearch.md) is enabled.
...
...
@@ -701,6 +710,7 @@ Example response:
{
"basename":"README",
"data":"```\n\n## Installation\n\nQuick start using the [pre-built",
"path":"README.md",
"filename":"README.md",
"id":null,
"ref":"master",
...
...
@@ -710,6 +720,8 @@ Example response:
]
```
**Note:**`filename` is deprecated in favor of `path`. Both return the full path of the file inside the repository, but in the future `filename` will be only the file name and not the full path (see [this issue][gitlab-34521]).
### Scope: users
```bash
...
...
@@ -981,6 +993,7 @@ Example response:
{
"basename":"home",
"data":"hello\n\nand bye\n\nend",
"path":"home.md",
"filename":"home.md",
"id":null,
"ref":"master",
...
...
@@ -990,6 +1003,8 @@ Example response:
]
```
**Note:**`filename` is deprecated in favor of `path`. Both return the full path of the file inside the repository, but in the future `filename` will be only the file name and not the full path (see [this issue][gitlab-34521]).
### Scope: commits
```bash
...
...
@@ -1051,6 +1066,7 @@ Example response:
{
"basename":"README",
"data":"```\n\n## Installation\n\nQuick start using the [pre-built",
"path":"README.md",
"filename":"README.md",
"id":null,
"ref":"master",
...
...
@@ -1060,6 +1076,8 @@ Example response:
]
```
**Note:**`filename` is deprecated in favor of `path`. Both return the full path of the file inside the repository, but in the future `filename` will be only the file name and not the full path (see [this issue][gitlab-34521]).
the [stable/cert-manager](https://github.com/helm/charts/tree/master/stable/cert-manager)
chart was used.
The chart used to install this application depends on the version of GitLab used. In:
NOTE: **Note:**
If you have installed cert-manager prior to GitLab 12.3, Let's Encrypt will
[block requests from older versions of cert-manager](https://community.letsencrypt.org/t/blocking-old-cert-manager-versions/98753).
To resolve this, uninstall cert-manager (consider [backing up any additional configuration](https://docs.cert-manager.io/en/latest/tasks/backup-restore-crds.html)), then install cert-manager again.
- GitLab 12.3 and newer, the [jetstack/cert-manager](https://github.com/jetstack/cert-manager)
chart is used with a [`values.yaml`](https://gitlab.com/gitlab-org/gitlab/blob/master/vendor/cert_manager/values.yaml)
file.
- GitLab 12.2 and older, the [stable/cert-manager](https://github.com/helm/charts/tree/master/stable/cert-manager)
chart was used.
If you have installed Cert-Manager prior to GitLab 12.3, Let's Encrypt will
[block requests from older versions of Cert-Manager](https://community.letsencrypt.org/t/blocking-old-cert-manager-versions/98753).
To resolve this:
1. Uninstall Cert-Manager (consider [backing up any additional configuration](https://docs.cert-manager.io/en/latest/tasks/backup-restore-crds.html)).
1. Install Cert-Manager again.
### GitLab Runner
...
...
@@ -296,7 +298,7 @@ The applications below can be uninstalled.
| Application | GitLab version | Notes |
| ----------- | -------------- | ----- |
| Cert-Manager | 12.2+ | The associated private key will be deleted and cannot be restored. Deployed applications will continue to use HTTPS, but certificates will not be renewed. Before uninstalling, you may wish to [back up your configuration](https://docs.cert-manager.io/en/latest/tasks/backup-restore-crds.html) or [revoke your certificates](https://letsencrypt.org/docs/revoking/) |
| Cert-Manager | 12.2+ | The associated private key will be deleted and cannot be restored. Deployed applications will continue to use HTTPS, but certificates will not be renewed. Before uninstalling, you may wish to [back up your configuration](https://docs.cert-manager.io/en/latest/tasks/backup-restore-crds.html) or [revoke your certificates](https://letsencrypt.org/docs/revoking/). |
| GitLab Runner | 12.2+ | Any running pipelines will be canceled. |
| Helm | 12.2+ | The associated Tiller pod, the `gitlab-managed-apps` namespace, and all of its resources will be deleted and cannot be restored. |
| Ingress | 12.1+ | The associated load balancer and IP will be deleted and cannot be restored. Furthermore, it can only be uninstalled if JupyterHub is not installed. |