kotovalexarian-likes-gitlab
/
gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity

Add latest changes from gitlab-org/gitlab@master

This commit is contained in:
GitLab Bot 2020-12-09 06:09:41 +00:00
parent a25cab22f8
commit 47d41a24a1
35 changed files with 82 additions and 79 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
.vale.ini
View File

@ -7,3 +7,6 @@ MinAlertLevel = suggestion
[*.md] [*.md]
BasedOnStyles = gitlab BasedOnStyles = gitlab
# Ignore SVG markup
TokenIgnores = (\*\*\{\w*\}\*\*)

2
doc/administration/consul.md
View File

@ -77,7 +77,7 @@ Identify any existing health issues in the cluster by running the following comm
within each node. The command will return an empty array if the cluster is healthy: within each node. The command will return an empty array if the cluster is healthy:
```shell ```shell
curl http://127.0.0.1:8500/v1/health/state/critical curl "http://127.0.0.1:8500/v1/health/state/critical"
``` ```
Consul nodes communicate using the raft protocol. If the current leader goes Consul nodes communicate using the raft protocol. If the current leader goes

2
doc/administration/geo/setup/database.md
View File

@ -151,7 +151,7 @@ There is an [issue where support is being discussed](https://gitlab.com/gitlab-o
## ##
## Public address ## Public address
## ##
echo "External address: $(curl --silent ipinfo.io/ip)" echo "External address: $(curl --silent "ipinfo.io/ip")"
``` ```
In most cases, the following addresses will be used to configure GitLab In most cases, the following addresses will be used to configure GitLab

2
doc/administration/invalidate_markdown_cache.md
View File

@ -19,5 +19,5 @@ be done by [changing the application settings through
the API](../api/settings.md#change-application-settings): the API](../api/settings.md#change-application-settings):
```shell ```shell
curl --request PUT --header "PRIVATE-TOKEN: <your_access_token>" https://gitlab.example.com/api/v4/application/settings?local_markdown_version=<increased_number> curl --request PUT --header "PRIVATE-TOKEN: <your_access_token>" "https://gitlab.example.com/api/v4/application/settings?local_markdown_version=<increased_number>"
``` ```

2
doc/administration/operations/fast_ssh_key_lookup.md
View File

@ -139,7 +139,7 @@ the database. The following instructions can be used to build OpenSSH 7.5:
```shell ```shell
sudo su - sudo su -
cd /tmp cd /tmp
curl --remote-name https://cdn.openbsd.org/pub/OpenBSD/OpenSSH/portable/openssh-7.5p1.tar.gz curl --remote-name "https://cdn.openbsd.org/pub/OpenBSD/OpenSSH/portable/openssh-7.5p1.tar.gz"
tar xzvf openssh-7.5p1.tar.gz tar xzvf openssh-7.5p1.tar.gz
yum install rpm-build gcc make wget openssl-devel krb5-devel pam-devel libX11-devel xmkmf libXt-devel yum install rpm-build gcc make wget openssl-devel krb5-devel pam-devel libX11-devel xmkmf libXt-devel
``` ```

6
doc/administration/packages/container_registry.md
View File

@ -1155,8 +1155,8 @@ After adding the setting, [reconfigure GitLab](../restart_gitlab.md#omnibus-gitl
Use curl to request debug output from the debug server: Use curl to request debug output from the debug server:
```shell ```shell
curl localhost:5001/debug/health curl "localhost:5001/debug/health"
curl localhost:5001/debug/vars curl "localhost:5001/debug/vars"
``` ```
### Advanced Troubleshooting ### Advanced Troubleshooting
@ -1236,7 +1236,7 @@ mitmproxy --port 9000
This command runs mitmproxy on port `9000`. In another window, run: This command runs mitmproxy on port `9000`. In another window, run:
```shell ```shell
curl --proxy http://localhost:9000 https://httpbin.org/status/200 curl --proxy "http://localhost:9000" "https://httpbin.org/status/200"
``` ```
If everything is set up correctly, information is displayed on the mitmproxy window and If everything is set up correctly, information is displayed on the mitmproxy window and

4
doc/administration/reference_architectures/troubleshooting.md
View File

@ -434,13 +434,13 @@ If the monitoring node is not receiving any data, check that the exporters are
capturing data. capturing data.
```shell ```shell
curl http[s]://localhost:<EXPORTER LISTENING PORT>/metric curl "http[s]://localhost:<EXPORTER LISTENING PORT>/metric"
``` ```
or or
```shell ```shell
curl http[s]://localhost:<EXPORTER LISTENING PORT>/-/metric curl "http[s]://localhost:<EXPORTER LISTENING PORT>/-/metric"
``` ```
## Troubleshooting PgBouncer ## Troubleshooting PgBouncer

4
doc/administration/snippets/index.md
View File

@ -64,11 +64,11 @@ The process to set the snippets size limit through the Application Settings API
exactly the same as you would do to [update any other setting](../../api/settings.md#change-application-settings). exactly the same as you would do to [update any other setting](../../api/settings.md#change-application-settings).
```shell ```shell
curl --request PUT --header "PRIVATE-TOKEN: <your_access_token>" https://gitlab.example.com/api/v4/application/settings?snippet_size_limit=52428800 curl --request PUT --header "PRIVATE-TOKEN: <your_access_token>" "https://gitlab.example.com/api/v4/application/settings?snippet_size_limit=52428800"
``` ```
You can also use the API to [retrieve the current value](../../api/settings.md#get-current-application-settings). You can also use the API to [retrieve the current value](../../api/settings.md#get-current-application-settings).
```shell ```shell
curl --header "PRIVATE-TOKEN: <your_access_token>" https://gitlab.example.com/api/v4/application/settings curl --header "PRIVATE-TOKEN: <your_access_token>" "https://gitlab.example.com/api/v4/application/settings"
``` ```

2
doc/administration/troubleshooting/linux_cheat_sheet.md
View File

@ -303,7 +303,7 @@ nslookup example.com 1.1.1.1
whois <ip_address> | grep -i "orgname\|netname" whois <ip_address> | grep -i "orgname\|netname"
# Curl headers with redirect # Curl headers with redirect
curl --head --location https://example.com curl --head --location "https://example.com"
``` ```
## Package Management ## Package Management

4
doc/administration/troubleshooting/ssl.md
View File

@ -24,7 +24,7 @@ following issues:
- `curl` fails: - `curl` fails:
```shell ```shell
curl https://gitlab.domain.tld curl "https://gitlab.domain.tld"
curl: (60) SSL certificate problem: unable to get local issuer certificate curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https://curl.haxx.se/docs/sslcerts.html More details here: https://curl.haxx.se/docs/sslcerts.html
``` ```
@ -125,7 +125,7 @@ The cause of the issue can be confirmed by checking if:
- `curl` fails: - `curl` fails:
```shell ```shell
$ curl https://gitlab.domain.tld $ curl "https://gitlab.domain.tld"
curl: (60) SSL certificate problem: self signed certificate curl: (60) SSL certificate problem: self signed certificate
More details here: https://curl.haxx.se/docs/sslcerts.html More details here: https://curl.haxx.se/docs/sslcerts.html
``` ```

2
doc/administration/troubleshooting/test_environments.md
View File

@ -103,7 +103,7 @@ docker run -d --name elasticsearch \
docker.elastic.co/elasticsearch/elasticsearch:5.5.1 docker.elastic.co/elasticsearch/elasticsearch:5.5.1
``` ```
Then confirm it works in the browser at `curl http://<IP_ADDRESS>:9200/_cat/health`. Then confirm it works in the browser at `curl "http://<IP_ADDRESS>:9200/_cat/health"`.
Elasticsearch's default username is `elastic` and password is `changeme`. Elasticsearch's default username is `elastic` and password is `changeme`.
### Kroki ### Kroki

2
doc/administration/troubleshooting/tracing_correlation_id.md
View File

@ -59,7 +59,7 @@ interested in.
If you're using `curl` then you can use the verbose option to show request and response headers, as well as other debug info. If you're using `curl` then you can use the verbose option to show request and response headers, as well as other debug info.
```shell ```shell
➜ ~ curl --verbose https://gitlab.example.com/api/v4/projects ➜ ~ curl --verbose "https://gitlab.example.com/api/v4/projects"
# look for a line that looks like this # look for a line that looks like this
< x-request-id: 4rAMkV3gof4 < x-request-id: 4rAMkV3gof4
``` ```

4
doc/administration/wikis/index.md
View File

@ -65,11 +65,11 @@ The process to set the wiki page size limit through the Application Settings API
exactly the same as you would do to [update any other setting](../../api/settings.md#change-application-settings). exactly the same as you would do to [update any other setting](../../api/settings.md#change-application-settings).
```shell ```shell
curl --request PUT --header "PRIVATE-TOKEN: <your_access_token>" https://gitlab.example.com/api/v4/application/settings?wiki_page_max_content_bytes=52428800 curl --request PUT --header "PRIVATE-TOKEN: <your_access_token>" "https://gitlab.example.com/api/v4/application/settings?wiki_page_max_content_bytes=52428800"
``` ```
You can also use the API to [retrieve the current value](../../api/settings.md#get-current-application-settings). You can also use the API to [retrieve the current value](../../api/settings.md#get-current-application-settings).
```shell ```shell
curl --header "PRIVATE-TOKEN: <your_access_token>" https://gitlab.example.com/api/v4/application/settings curl --header "PRIVATE-TOKEN: <your_access_token>" "https://gitlab.example.com/api/v4/application/settings"
``` ```

2
doc/api/freeze_periods.md
View File

@ -138,7 +138,7 @@ Example request:
```shell ```shell
curl --header 'Content-Type: application/json' --header "PRIVATE-TOKEN: <your_access_token>" \ curl --header 'Content-Type: application/json' --header "PRIVATE-TOKEN: <your_access_token>" \
--data '{ "freeze_end": "0 8 * * 1" }' \ --data '{ "freeze_end": "0 8 * * 1" }' \
--request PUT https://gitlab.example.com/api/v4/projects/19/freeze_periods/1 --request PUT "https://gitlab.example.com/api/v4/projects/19/freeze_periods/1"
``` ```
Example response: Example response:

4
doc/api/metrics_user_starred_dashboards.md
View File

@ -26,7 +26,7 @@ Parameters:
| `dashboard_path` | string | yes | URL-encoded path to file defining the dashboard which should be marked as favorite. | | `dashboard_path` | string | yes | URL-encoded path to file defining the dashboard which should be marked as favorite. |
```shell ```shell
curl --header 'Private-Token: <your_access_token>' https://gitlab.example.com/api/v4/projects/20/metrics/user_starred_dashboards \ curl --header 'Private-Token: <your_access_token>' "https://gitlab.example.com/api/v4/projects/20/metrics/user_starred_dashboards" \
--data-urlencode "dashboard_path=config/prometheus/dashboards/common_metrics.yml" --data-urlencode "dashboard_path=config/prometheus/dashboards/common_metrics.yml"
``` ```
@ -57,7 +57,7 @@ Parameters:
| `dashboard_path` | string | no | URL-encoded path to file defining the dashboard which should no longer be marked as favorite. When not supplied, all dashboards within given projects are removed from favorites. | | `dashboard_path` | string | no | URL-encoded path to file defining the dashboard which should no longer be marked as favorite. When not supplied, all dashboards within given projects are removed from favorites. |
```shell ```shell
curl --request DELETE --header 'Private-Token: <your_access_token>' https://gitlab.example.com/api/v4/projects/20/metrics/user_starred_dashboards \ curl --request DELETE --header 'Private-Token: <your_access_token>' "https://gitlab.example.com/api/v4/projects/20/metrics/user_starred_dashboards" \
--data-urlencode "dashboard_path=config/prometheus/dashboards/common_metrics.yml" --data-urlencode "dashboard_path=config/prometheus/dashboards/common_metrics.yml"
``` ```

2
doc/ci/ci_cd_for_external_repos/bitbucket_integration.md
View File

@ -110,7 +110,7 @@ To use GitLab CI/CD with a Bitbucket Cloud repository:
esac esac
echo "Pushing status to $BITBUCKET_STATUS_API..." echo "Pushing status to $BITBUCKET_STATUS_API..."
curl --request POST $BITBUCKET_STATUS_API \ curl --request POST "$BITBUCKET_STATUS_API" \
--user $BITBUCKET_USERNAME:$BITBUCKET_ACCESS_TOKEN \ --user $BITBUCKET_USERNAME:$BITBUCKET_ACCESS_TOKEN \
--header "Content-Type:application/json" \ --header "Content-Type:application/json" \
--silent \ --silent \

2
doc/ci/examples/laravel_with_gitlab_and_envoy/index.md
View File

@ -417,7 +417,7 @@ RUN apt-get clean
RUN docker-php-ext-install mcrypt pdo_mysql zip RUN docker-php-ext-install mcrypt pdo_mysql zip
# Install Composer # Install Composer
RUN curl --silent --show-error https://getcomposer.org/installer | php -- --install-dir=/usr/local/bin --filename=composer RUN curl --silent --show-error "https://getcomposer.org/installer" | php -- --install-dir=/usr/local/bin --filename=composer
# Install Laravel Envoy # Install Laravel Envoy
RUN composer global require "laravel/envoy=~1.0" RUN composer global require "laravel/envoy=~1.0"

2
doc/ci/examples/php.md
View File

@ -56,7 +56,7 @@ apt-get update -yqq
apt-get install git -yqq apt-get install git -yqq
# Install phpunit, the tool that we will use for testing # Install phpunit, the tool that we will use for testing
curl --location --output /usr/local/bin/phpunit https://phar.phpunit.de/phpunit.phar curl --location --output /usr/local/bin/phpunit "https://phar.phpunit.de/phpunit.phar"
chmod +x /usr/local/bin/phpunit chmod +x /usr/local/bin/phpunit
# Install mysql driver # Install mysql driver

8
doc/ci/triggers/README.md
View File

@ -56,7 +56,7 @@ and it creates a dependent pipeline relation visible on the
build_docs: build_docs:
stage: deploy stage: deploy
script: script:
- curl --request POST --form "token=$CI_JOB_TOKEN" --form ref=master https://gitlab.example.com/api/v4/projects/9/trigger/pipeline - curl --request POST --form "token=$CI_JOB_TOKEN" --form ref=master "https://gitlab.example.com/api/v4/projects/9/trigger/pipeline"
only: only:
- tags - tags
``` ```
@ -143,7 +143,7 @@ By using cURL you can trigger a pipeline rerun with minimal effort, for example:
curl --request POST \ curl --request POST \
--form token=TOKEN \ --form token=TOKEN \
--form ref=master \ --form ref=master \
https://gitlab.example.com/api/v4/projects/9/trigger/pipeline "https://gitlab.example.com/api/v4/projects/9/trigger/pipeline"
``` ```
In this case, the project with ID `9` gets rebuilt on `master` branch. In this case, the project with ID `9` gets rebuilt on `master` branch.
@ -244,7 +244,7 @@ curl --request POST \
--form token=TOKEN \ --form token=TOKEN \
--form ref=master \ --form ref=master \
--form "variables[UPLOAD_TO_S3]=true" \ --form "variables[UPLOAD_TO_S3]=true" \
https://gitlab.example.com/api/v4/projects/9/trigger/pipeline "https://gitlab.example.com/api/v4/projects/9/trigger/pipeline"
``` ```
Trigger variables have the [highest priority](../variables/README.md#priority-of-environment-variables) Trigger variables have the [highest priority](../variables/README.md#priority-of-environment-variables)
@ -257,7 +257,7 @@ in conjunction with cron. The example below triggers a job on the `master`
branch of project with ID `9` every night at `00:30`: branch of project with ID `9` every night at `00:30`:
```shell ```shell
30 0 * * * curl --request POST --form token=TOKEN --form ref=master https://gitlab.example.com/api/v4/projects/9/trigger/pipeline 30 0 * * * curl --request POST --form token=TOKEN --form ref=master "https://gitlab.example.com/api/v4/projects/9/trigger/pipeline"
``` ```
This behavior can also be achieved through GitLab's UI with This behavior can also be achieved through GitLab's UI with

2
doc/ci/yaml/README.md
View File

@ -4257,7 +4257,7 @@ job_name:
- *some-script-before - *some-script-before
script: script:
- *some-script - *some-script
before_script: after_script:
- *some-script-after - *some-script-after
``` ```

20
doc/development/chaos_endpoints.md
View File

@ -66,8 +66,8 @@ GET /-/chaos/leakmem?memory_mb=1024&duration_s=50&async=true
| `async` | boolean | no | Set to true to leak memory in a Sidekiq background worker process | | `async` | boolean | no | Set to true to leak memory in a Sidekiq background worker process |
```shell ```shell
curl http://localhost:3000/-/chaos/leakmem?memory_mb=1024&duration_s=10 --header 'X-Chaos-Secret: secret' curl "http://localhost:3000/-/chaos/leakmem?memory_mb=1024&duration_s=10" --header 'X-Chaos-Secret: secret'
curl http://localhost:3000/-/chaos/leakmem?memory_mb=1024&duration_s=10&token=secret curl "http://localhost:3000/-/chaos/leakmem?memory_mb=1024&duration_s=10&token=secret"
``` ```
## CPU spin ## CPU spin
@ -89,8 +89,8 @@ GET /-/chaos/cpu_spin?duration_s=50&async=true
| `async` | boolean | no | Set to true to consume CPU in a Sidekiq background worker process | | `async` | boolean | no | Set to true to consume CPU in a Sidekiq background worker process |
```shell ```shell
curl http://localhost:3000/-/chaos/cpu_spin?duration_s=60 --header 'X-Chaos-Secret: secret' curl "http://localhost:3000/-/chaos/cpu_spin?duration_s=60" --header 'X-Chaos-Secret: secret'
curl http://localhost:3000/-/chaos/cpu_spin?duration_s=60&token=secret curl "http://localhost:3000/-/chaos/cpu_spin?duration_s=60&token=secret"
``` ```
## DB spin ## DB spin
@ -114,8 +114,8 @@ GET /-/chaos/db_spin?duration_s=50&async=true
| `async` | boolean | no | Set to true to perform the operation in a Sidekiq background worker process | | `async` | boolean | no | Set to true to perform the operation in a Sidekiq background worker process |
```shell ```shell
curl http://localhost:3000/-/chaos/db_spin?interval_s=1&duration_s=60 --header 'X-Chaos-Secret: secret' curl "http://localhost:3000/-/chaos/db_spin?interval_s=1&duration_s=60" --header 'X-Chaos-Secret: secret'
curl http://localhost:3000/-/chaos/db_spin?interval_s=1&duration_s=60&token=secret curl "http://localhost:3000/-/chaos/db_spin?interval_s=1&duration_s=60&token=secret"
``` ```
## Sleep ## Sleep
@ -136,8 +136,8 @@ GET /-/chaos/sleep?duration_s=50&async=true
| `async` | boolean | no | Set to true to sleep in a Sidekiq background worker process | | `async` | boolean | no | Set to true to sleep in a Sidekiq background worker process |
```shell ```shell
curl http://localhost:3000/-/chaos/sleep?duration_s=60 --header 'X-Chaos-Secret: secret' curl "http://localhost:3000/-/chaos/sleep?duration_s=60" --header 'X-Chaos-Secret: secret'
curl http://localhost:3000/-/chaos/sleep?duration_s=60&token=secret curl "http://localhost:3000/-/chaos/sleep?duration_s=60&token=secret"
``` ```
## Kill ## Kill
@ -157,6 +157,6 @@ GET /-/chaos/kill?async=true
| `async` | boolean | no | Set to true to kill a Sidekiq background worker process | | `async` | boolean | no | Set to true to kill a Sidekiq background worker process |
```shell ```shell
curl http://localhost:3000/-/chaos/kill --header 'X-Chaos-Secret: secret' curl "http://localhost:3000/-/chaos/kill" --header 'X-Chaos-Secret: secret'
curl http://localhost:3000/-/chaos/kill?token=secret curl "http://localhost:3000/-/chaos/kill?token=secret"
``` ```

4
doc/development/gitaly.md
View File

@ -345,7 +345,7 @@ the integration by using GDK:
1. Check that the list of current metrics has the new counter for the feature flag: 1. Check that the list of current metrics has the new counter for the feature flag:
```shell ```shell
curl --silent http://localhost:9236/metrics | grep go_find_all_tags curl --silent "http://localhost:9236/metrics" | grep go_find_all_tags
``` ```
1. Once you observe the metrics for the new feature flag and it increments, you 1. Once you observe the metrics for the new feature flag and it increments, you
@ -375,5 +375,5 @@ the integration by using GDK:
1. Verify the feature is on by observing the metrics for it: 1. Verify the feature is on by observing the metrics for it:
```shell ```shell
curl --silent http://localhost:9236/metrics | grep go_find_all_tags curl --silent "http://localhost:9236/metrics" | grep go_find_all_tags
``` ```

14
doc/development/internal_api.md
View File

@ -60,7 +60,7 @@ POST /internal/allowed
Example request: Example request:
```shell ```shell
curl --request POST --header "Gitlab-Shared-Secret: <Base64 encoded token>" --data "key_id=11&project=gnuwget/wget2&action=git-upload-pack&protocol=ssh" http://localhost:3001/api/v4/internal/allowed curl --request POST --header "Gitlab-Shared-Secret: <Base64 encoded token>" --data "key_id=11&project=gnuwget/wget2&action=git-upload-pack&protocol=ssh" "http://localhost:3001/api/v4/internal/allowed"
``` ```
Example response: Example response:
@ -108,7 +108,7 @@ information for LFS clients when the repository is accessed over SSH.
Example request: Example request:
```shell ```shell
curl --request POST --header "Gitlab-Shared-Secret: <Base64 encoded token>" --data "key_id=11&project=gnuwget/wget2" http://localhost:3001/api/v4/internal/lfs_authenticate curl --request POST --header "Gitlab-Shared-Secret: <Base64 encoded token>" --data "key_id=11&project=gnuwget/wget2" "http://localhost:3001/api/v4/internal/lfs_authenticate"
``` ```
```json ```json
@ -141,7 +141,7 @@ GET /internal/authorized_keys
Example request: Example request:
```shell ```shell
curl --request GET --header "Gitlab-Shared-Secret: <Base64 encoded secret>""http://localhost:3001/api/v4/internal/authorized_keys?key=<key as passed by OpenSSH>" curl --request GET --header "Gitlab-Shared-Secret: <Base64 encoded secret>" "http://localhost:3001/api/v4/internal/authorized_keys?key=<key as passed by OpenSSH>"
``` ```
Example response: Example response:
@ -242,7 +242,7 @@ GET /internal/two_factor_recovery_codes
Example request: Example request:
```shell ```shell
curl --request POST --header "Gitlab-Shared-Secret: <Base64 encoded secret>" --data "key_id=7" http://localhost:3001/api/v4/internal/two_factor_recovery_codes curl --request POST --header "Gitlab-Shared-Secret: <Base64 encoded secret>" --data "key_id=7" "http://localhost:3001/api/v4/internal/two_factor_recovery_codes"
``` ```
Example response: Example response:
@ -289,7 +289,7 @@ POST /internal/personal_access_token
Example request: Example request:
```shell ```shell
curl --request POST --header "Gitlab-Shared-Secret: <Base64 encoded secret>" --data "user_id=29&name=mytokenname&scopes[]=read_user&scopes[]=read_repository&expires_at=2020-07-24" http://localhost:3001/api/v4/internal/personal_access_token curl --request POST --header "Gitlab-Shared-Secret: <Base64 encoded secret>" --data "user_id=29&name=mytokenname&scopes[]=read_user&scopes[]=read_repository&expires_at=2020-07-24" "http://localhost:3001/api/v4/internal/personal_access_token"
``` ```
Example response: Example response:
@ -323,7 +323,7 @@ POST /internal/pre_receive
Example request: Example request:
```shell ```shell
curl --request POST --header "Gitlab-Shared-Secret: <Base64 encoded secret>" --data "gl_repository=project-7" http://localhost:3001/api/v4/internal/pre_receive curl --request POST --header "Gitlab-Shared-Secret: <Base64 encoded secret>" --data "gl_repository=project-7" "http://localhost:3001/api/v4/internal/pre_receive"
``` ```
Example response: Example response:
@ -355,7 +355,7 @@ POST /internal/post_receive
Example Request: Example Request:
```shell ```shell
curl --request POST --header "Gitlab-Shared-Secret: <Base64 encoded secret>" --data "gl_repository=project-7" --data "identifier=user-1" --data "changes=0000000000000000000000000000000000000000 fd9e76b9136bdd9fe217061b497745792fe5a5ee gh-pages\n" http://localhost:3001/api/v4/internal/post_receive curl --request POST --header "Gitlab-Shared-Secret: <Base64 encoded secret>" --data "gl_repository=project-7" --data "identifier=user-1" --data "changes=0000000000000000000000000000000000000000 fd9e76b9136bdd9fe217061b497745792fe5a5ee gh-pages\n" "http://localhost:3001/api/v4/internal/post_receive"
``` ```
Example response: Example response:

2
doc/development/python_guide/index.md
View File

@ -30,7 +30,7 @@ brew install pyenv
To install `pyenv` on Linux, you can run the command below: To install `pyenv` on Linux, you can run the command below:
```shell ```shell
curl https://pyenv.run | bash curl "https://pyenv.run" | bash
``` ```
Alternatively, you may find `pyenv` available as a system package via your distro package manager. Alternatively, you may find `pyenv` available as a system package via your distro package manager.

8
doc/install/installation.md
View File

@ -215,7 +215,7 @@ Download Ruby and compile it:
```shell ```shell
mkdir /tmp/ruby && cd /tmp/ruby mkdir /tmp/ruby && cd /tmp/ruby
curl --remote-name --progress https://cache.ruby-lang.org/pub/ruby/2.7/ruby-2.7.2.tar.gz curl --remote-name --progress "https://cache.ruby-lang.org/pub/ruby/2.7/ruby-2.7.2.tar.gz"
echo 'cb9731a17487e0ad84037490a6baf8bfa31a09e8 ruby-2.7.2.tar.gz' | shasum -c - && tar xzf ruby-2.7.2.tar.gz echo 'cb9731a17487e0ad84037490a6baf8bfa31a09e8 ruby-2.7.2.tar.gz' | shasum -c - && tar xzf ruby-2.7.2.tar.gz
cd ruby-2.7.2 cd ruby-2.7.2
@ -235,7 +235,7 @@ page](https://golang.org/dl).
# Remove former Go installation folder # Remove former Go installation folder
sudo rm -rf /usr/local/go sudo rm -rf /usr/local/go
curl --remote-name --progress https://dl.google.com/go/go1.13.5.linux-amd64.tar.gz curl --remote-name --progress "https://dl.google.com/go/go1.13.5.linux-amd64.tar.gz"
echo '512103d7ad296467814a6e3f635631bd35574cab3369a97a323c9a585ccaa569 go1.13.5.linux-amd64.tar.gz' | shasum -a256 -c - && \ echo '512103d7ad296467814a6e3f635631bd35574cab3369a97a323c9a585ccaa569 go1.13.5.linux-amd64.tar.gz' | shasum -a256 -c - && \
sudo tar -C /usr/local -xzf go1.13.5.linux-amd64.tar.gz sudo tar -C /usr/local -xzf go1.13.5.linux-amd64.tar.gz
sudo ln -sf /usr/local/go/bin/{go,godoc,gofmt} /usr/local/bin/ sudo ln -sf /usr/local/go/bin/{go,godoc,gofmt} /usr/local/bin/
@ -257,10 +257,10 @@ we need to install through the following commands:
```shell ```shell
# install node v12.x # install node v12.x
curl --location https://deb.nodesource.com/setup_12.x | sudo bash - curl --location "https://deb.nodesource.com/setup_12.x" | sudo bash -
sudo apt-get install -y nodejs sudo apt-get install -y nodejs
curl --silent --show-error https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add - curl --silent --show-error "https://dl.yarnpkg.com/debian/pubkey.gpg" | sudo apt-key add -
echo "deb https://dl.yarnpkg.com/debian/ stable main" | sudo tee /etc/apt/sources.list.d/yarn.list echo "deb https://dl.yarnpkg.com/debian/ stable main" | sudo tee /etc/apt/sources.list.d/yarn.list
sudo apt-get update sudo apt-get update
sudo apt-get install yarn sudo apt-get install yarn

4
doc/migrate_ci_to_ce/README.md
View File

@ -324,8 +324,8 @@ properly forward the requests.**
You should also make sure that you can: You should also make sure that you can:
1. `curl https://YOUR_GITLAB_SERVER_FQDN/` from your previous GitLab CI server. 1. `curl "https://YOUR_GITLAB_SERVER_FQDN/"` from your previous GitLab CI server.
1. `curl https://YOUR_CI_SERVER_FQDN/` from your GitLab CE (or EE) server. 1. `curl "https://YOUR_CI_SERVER_FQDN/"` from your GitLab CE (or EE) server.
### 2. Check NGINX configuration ### 2. Check NGINX configuration

2
doc/topics/autodevops/customize.md
View File

@ -662,5 +662,5 @@ The banner can be disabled for:
- Through the REST API with an admin access token: - Through the REST API with an admin access token:
```shell ```shell
curl --data "value=true" --header "PRIVATE-TOKEN: <personal_access_token>" https://gitlab.example.com/api/v4/features/auto_devops_banner_disabled curl --data "value=true" --header "PRIVATE-TOKEN: <personal_access_token>" "https://gitlab.example.com/api/v4/features/auto_devops_banner_disabled"
``` ```

4
doc/topics/web_application_firewall/quick_start_guide.md
View File

@ -201,7 +201,7 @@ your cluster either using [Cloud Shell](https://cloud.google.com/shell/) or the
NAME HOSTS PORTS NAME HOSTS PORTS
production-auto-deploy fjdiaz-auto-devv-2.34.68.60.207.nip.io,le-16730183.34.68.60.207.nip.io 80, 443 production-auto-deploy fjdiaz-auto-devv-2.34.68.60.207.nip.io,le-16730183.34.68.60.207.nip.io 80, 443
$ curl --location --insecure fjdiaz-auto-devv-2.34.68.60.207.nip.io | grep 'Rails!' --after 2 --before 2 $ curl --location --insecure "fjdiaz-auto-devv-2.34.68.60.207.nip.io" | grep 'Rails!' --after 2 --before 2
<body> <body>
<p>You're on Rails!</p> <p>You're on Rails!</p>
</body> </body>
@ -216,7 +216,7 @@ Now let's send a potentially malicious request, as if we were a scanner,
checking for vulnerabilities within our application and examine the ModSecurity logs: checking for vulnerabilities within our application and examine the ModSecurity logs:
```shell ```shell
$ curl --location --insecure fjdiaz-auto-devv-2.34.68.60.207.nip.io --header "User-Agent: absinthe" | grep 'Rails!' --after 2 --before 2 $ curl --location --insecure "fjdiaz-auto-devv-2.34.68.60.207.nip.io" --header "User-Agent: absinthe" | grep 'Rails!' --after 2 --before 2
<body> <body>
<p>You're on Rails!</p> <p>You're on Rails!</p>
</body> </body>

10
doc/update/upgrading_from_source.md
View File

@ -70,7 +70,7 @@ Download Ruby and compile it:
```shell ```shell
mkdir /tmp/ruby && cd /tmp/ruby mkdir /tmp/ruby && cd /tmp/ruby
curl --remote-name --progress https://cache.ruby-lang.org/pub/ruby/2.7/ruby-2.7.2.tar.gz curl --remote-name --progress "https://cache.ruby-lang.org/pub/ruby/2.7/ruby-2.7.2.tar.gz"
echo 'cb9731a17487e0ad84037490a6baf8bfa31a09e8 ruby-2.7.2.tar.gz' | shasum -c - && tar xzf ruby-2.7.2.tar.gz echo 'cb9731a17487e0ad84037490a6baf8bfa31a09e8 ruby-2.7.2.tar.gz' | shasum -c - && tar xzf ruby-2.7.2.tar.gz
cd ruby-2.7.2 cd ruby-2.7.2
@ -89,7 +89,7 @@ dependencies.
In Debian or Ubuntu: In Debian or Ubuntu:
```shell ```shell
curl --silent --show-error https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add - curl --silent --show-error "https://dl.yarnpkg.com/debian/pubkey.gpg" | sudo apt-key add -
echo "deb https://dl.yarnpkg.com/debian/ stable main" | sudo tee /etc/apt/sources.list.d/yarn.list echo "deb https://dl.yarnpkg.com/debian/ stable main" | sudo tee /etc/apt/sources.list.d/yarn.list
sudo apt-get update sudo apt-get update
sudo apt-get install yarn sudo apt-get install yarn
@ -109,7 +109,7 @@ Download and install Go (for Linux, 64-bit):
# Remove former Go installation folder # Remove former Go installation folder
sudo rm -rf /usr/local/go sudo rm -rf /usr/local/go
curl --remote-name --progress https://dl.google.com/go/go1.13.5.linux-amd64.tar.gz curl --remote-name --progress "https://dl.google.com/go/go1.13.5.linux-amd64.tar.gz"
echo '512103d7ad296467814a6e3f635631bd35574cab3369a97a323c9a585ccaa569 go1.13.5.linux-amd64.tar.gz' | shasum -a256 -c - && \ echo '512103d7ad296467814a6e3f635631bd35574cab3369a97a323c9a585ccaa569 go1.13.5.linux-amd64.tar.gz' | shasum -a256 -c - && \
sudo tar -C /usr/local -xzf go1.13.5.linux-amd64.tar.gz sudo tar -C /usr/local -xzf go1.13.5.linux-amd64.tar.gz
sudo ln -sf /usr/local/go/bin/{go,godoc,gofmt} /usr/local/bin/ sudo ln -sf /usr/local/go/bin/{go,godoc,gofmt} /usr/local/bin/
@ -139,7 +139,7 @@ sudo apt-get remove git-core
sudo apt-get install -y libcurl4-openssl-dev libexpat1-dev gettext libz-dev libssl-dev build-essential sudo apt-get install -y libcurl4-openssl-dev libexpat1-dev gettext libz-dev libssl-dev build-essential
# Download and compile pcre2 from source # Download and compile pcre2 from source
curl --silent --show-error --location https://ftp.pcre.org/pub/pcre/pcre2-10.33.tar.gz --output pcre2.tar.gz curl --silent --show-error --location "https://ftp.pcre.org/pub/pcre/pcre2-10.33.tar.gz" --output pcre2.tar.gz
tar -xzf pcre2.tar.gz tar -xzf pcre2.tar.gz
cd pcre2-10.33 cd pcre2-10.33
chmod +x configure chmod +x configure
@ -149,7 +149,7 @@ make install
# Download and compile from source # Download and compile from source
cd /tmp cd /tmp
curl --remote-name --location --progress https://www.kernel.org/pub/software/scm/git/git-2.29.0.tar.gz curl --remote-name --location --progress "https://www.kernel.org/pub/software/scm/git/git-2.29.0.tar.gz"
echo 'fa08dc8424ef80c0f9bf307877f9e2e49f1a6049e873530d6747c2be770742ff git-2.29.0.tar.gz' | shasum -a256 -c - && tar -xzf git-2.29.0.tar.gz echo 'fa08dc8424ef80c0f9bf307877f9e2e49f1a6049e873530d6747c2be770742ff git-2.29.0.tar.gz' | shasum -a256 -c - && tar -xzf git-2.29.0.tar.gz
cd git-2.29.0/ cd git-2.29.0/
./configure --with-libpcre ./configure --with-libpcre

6
doc/user/admin_area/license.md
View File

@ -32,7 +32,7 @@ is locked.
## Uploading your license ## Uploading your license
The very first time you visit your GitLab EE installation signed in as an admin, The very first time you visit your GitLab EE installation signed in as an administrator,
you should see a note urging you to upload a license with a link that takes you you should see a note urging you to upload a license with a link that takes you
to **Admin Area > License**. to **Admin Area > License**.
@ -94,13 +94,13 @@ You can review the license details at any time in the **License** section of the
## Notification before the license expires ## Notification before the license expires
One month before the license expires, a message informing about the expiration One month before the license expires, a message informing about the expiration
date is displayed to GitLab admins. Make sure that you update your date is displayed to GitLab administrators. Make sure that you update your
license, otherwise you miss all the paid features if your license expires. license, otherwise you miss all the paid features if your license expires.
## What happens when your license expires ## What happens when your license expires
In case your license expires, GitLab locks down some features like Git pushes, In case your license expires, GitLab locks down some features like Git pushes,
and issue creation, and displays a message to all admins to inform of the expired license. and issue creation, and displays a message to all administrators to inform of the expired license.
To get back all the previous functionality, you must upload a new license. To get back all the previous functionality, you must upload a new license.
To fall back to having only the Core features active, you must delete the To fall back to having only the Core features active, you must delete the

6
doc/user/admin_area/monitoring/health_check.md
View File

@ -55,7 +55,7 @@ GET /-/health
Example request: Example request:
```shell ```shell
curl 'https://gitlab.example.com/-/health' curl "https://gitlab.example.com/-/health"
``` ```
Example response: Example response:
@ -82,7 +82,7 @@ GET /-/readiness?all=1
Example request: Example request:
```shell ```shell
curl 'https://gitlab.example.com/-/readiness' curl "https://gitlab.example.com/-/readiness"
``` ```
Example response: Example response:
@ -121,7 +121,7 @@ GET /-/liveness
Example request: Example request:
```shell ```shell
curl 'https://gitlab.example.com/-/liveness' curl "https://gitlab.example.com/-/liveness"
``` ```
Example response: Example response:

2
doc/user/packages/container_registry/index.md
View File

@ -577,7 +577,7 @@ Examples:
- Select all tags, keep at least 1 tag per image, clean up any tag older than 14 days, run once a month, preserve any images with the name `master` and the policy is enabled: - Select all tags, keep at least 1 tag per image, clean up any tag older than 14 days, run once a month, preserve any images with the name `master` and the policy is enabled:
```shell ```shell
curl --request PUT --header 'Content-Type: application/json;charset=UTF-8' --header "PRIVATE-TOKEN: <your_access_token>" --data-binary '{"container_expiration_policy_attributes":{"cadence":"1month","enabled":true,"keep_n":1,"older_than":"14d","name_regex":"","name_regex_delete":".*","name_regex_keep":".*-master"}}' 'https://gitlab.example.com/api/v4/projects/2' curl --request PUT --header 'Content-Type: application/json;charset=UTF-8' --header "PRIVATE-TOKEN: <your_access_token>" --data-binary '{"container_expiration_policy_attributes":{"cadence":"1month","enabled":true,"keep_n":1,"older_than":"14d","name_regex":"","name_regex_delete":".*","name_regex_keep":".*-master"}}' "https://gitlab.example.com/api/v4/projects/2"
``` ```
See the API documentation for further details: [Edit project](../../../api/projects.md#edit-project). See the API documentation for further details: [Edit project](../../../api/projects.md#edit-project).

6
doc/user/packages/generic_packages/index.md
View File

@ -49,7 +49,7 @@ Example request:
```shell ```shell
curl --header "PRIVATE-TOKEN: <your_access_token>" \ curl --header "PRIVATE-TOKEN: <your_access_token>" \
--upload-file path/to/file.txt \ --upload-file path/to/file.txt \
https://gitlab.example.com/api/v4/projects/24/packages/generic/my_package/0.0.1/file.txt "https://gitlab.example.com/api/v4/projects/24/packages/generic/my_package/0.0.1/file.txt"
``` ```
Example response: Example response:
@ -85,7 +85,7 @@ Example request that uses a personal access token:
```shell ```shell
curl --header "PRIVATE-TOKEN: <your_access_token>" \ curl --header "PRIVATE-TOKEN: <your_access_token>" \
https://gitlab.example.com/api/v4/projects/24/packages/generic/my_package/0.0.1/file.txt "https://gitlab.example.com/api/v4/projects/24/packages/generic/my_package/0.0.1/file.txt"
``` ```
## Publish a generic package by using CI/CD ## Publish a generic package by using CI/CD
@ -105,7 +105,7 @@ stages:
upload: upload:
stage: upload stage: upload
script: script:
- 'curl --header "JOB-TOKEN: $CI_JOB_TOKEN" --upload-file path/to/file.txt ${CI_API_V4_URL}/projects/${CI_PROJECT_ID}/packages/generic/my_package/0.0.1/file.txt' - 'curl --header "JOB-TOKEN: $CI_JOB_TOKEN" --upload-file path/to/file.txt "${CI_API_V4_URL}/projects/${CI_PROJECT_ID}/packages/generic/my_package/0.0.1/file.txt"'
download: download:
stage: download stage: download

8
doc/user/project/clusters/serverless/aws.md
View File

@ -157,7 +157,7 @@ Running the following `curl` command should trigger your function.
Your URL should be the one retrieved from the GitLab deploy stage log: Your URL should be the one retrieved from the GitLab deploy stage log:
```shell ```shell
curl https://u768nzby1j.execute-api.us-east-1.amazonaws.com/production/hello curl "https://u768nzby1j.execute-api.us-east-1.amazonaws.com/production/hello"
``` ```
That should output: That should output:
@ -200,7 +200,7 @@ The `serverless-offline` plugin allows to run your code locally. To run your cod
Running the following `curl` command should trigger your function. Running the following `curl` command should trigger your function.
```shell ```shell
curl http://localhost:3000/hello curl "http://localhost:3000/hello"
``` ```
It should output: It should output:
@ -444,7 +444,7 @@ To test the application you deployed, please go to the build log and follow the
1. Use curl to test the API. For example: 1. Use curl to test the API. For example:
```shell ```shell
curl https://py4rg7qtlg.execute-api.us-east-1.amazonaws.com/Prod/hello/ curl "https://py4rg7qtlg.execute-api.us-east-1.amazonaws.com/Prod/hello/"
``` ```
Output should be: Output should be:
@ -496,7 +496,7 @@ listening on `localhost:3000`.
Call the `hello` API by running: Call the `hello` API by running:
```shell ```shell
curl http://127.0.0.1:3000/hello curl "http://127.0.0.1:3000/hello"
``` ```
Output again should be: Output again should be:

4
doc/user/project/clusters/serverless/index.md
View File

@ -376,7 +376,7 @@ The sample function can now be triggered from any HTTP client using a simple `PO
--header "Content-Type: application/json" \ --header "Content-Type: application/json" \
--request POST \ --request POST \
--data '{"GitLab":"FaaS"}' \ --data '{"GitLab":"FaaS"}' \
http://functions-echo.functions-1.functions.example.com/ "http://functions-echo.functions-1.functions.example.com/"
``` ```
1. Using a web-based tool (such as Postman or Restlet) 1. Using a web-based tool (such as Postman or Restlet)
@ -443,7 +443,7 @@ To run a function locally:
1. Invoke your function: 1. Invoke your function:
```shell ```shell
curl http://localhost:8080 curl "http://localhost:8080"
``` ```
## Deploying Serverless applications ## Deploying Serverless applications