Start by moving this file into the new folder.

We don't need to allow irregular quotes, as it could
allow some tests to be avoided if the test looks for
the standard style only

Jonas Wälter authored 3 years ago and Imre (Admin) committed 3 years ago

Currently OAuth applications can be only global or per-user.  This adds
applications on a group level.

Update tier badge to indicate self-managed.

- Many missing commas
- Some wording improvements

This is to use more consistent language and Advanced Search migration
is clearer about the specific scope.

This documentation will likely help customers resolve a range of
problems. We regularly see customers trying to solve index problems by
guessing at a variety of different rake tasks or buttons in the UI. This
is the only sure way to fix a broken index state and it could hopefully
help them from running a bunch of other steps that are designed for
different purposes.

This will also be necessary for anyone that accidentally skips the
documentation for major version upgrades and misses some migrations
before they are deleted.

This is the first step to making it clear to operators about what they
need to check before proceeding with a major version upgrade as well as
hopefully helping them debug and fix any problems before proceeding.

We are also going to be removing the migration code from previous
versions in the major version upgrade so it's very important the
migration completes before the upgrade otherwise it will just fail as
it will be a blank migration.

The previous merge request removed a deprecated wiki link from the
page, but the following sentence needed to be redacted too. This
merge request handles that work.

Remove images no longer in use on any page

We have two pages referring to the advanced search that
can be merged into one.

This change introduces a new rake task estimate_cluster_size,
which could be useful for estimating ES cluster size

This will help people diagnose if there are pending migrations before
doing upgrades that might cause backwards compatibility issues.

Handle another round of spelling issues in whatever ways seem best.

By default, `azure_activedirectory_v2` is the default path, but this
can be configured via the `name` parameter.

Related to: https://gitlab.com/gitlab-org/gitlab/-/issues/300312

This brings in the OmniAuth provider defined in
https://github.com/RIPGlobal/omniauth-azure-activedirectory-v2. The v1
endpoints do not seem to trigger MFA, which prevents logins when MFA is
enforced via Azure's Conditional Access policy.

Note that existing identities with the legacy V1 Azure provider do not
work, and users will either have to reconnect their GitLab accounts or
admins have to enable the auto-link feature.

Note that the following permission scopes are required for the
registered Web application:

1. profile
2. openid
3. email

In addition, a redirect URI for
`/users/auth/azure_activedirectory_v2/callback` has to be added to the
Web application.

Relates to:

1. https://gitlab.com/gitlab-org/gitlab/-/issues/214390
2. https://gitlab.com/gitlab-org/gitlab/-/issues/215674

Percentage encoding gets required for all special characters used in the
username or password supplied in the ElasticSearch URL.

Add the correct spellings to the allowed-words list, and put
suggestion-level substitutions in the correct substitutions file.

Relates to:

* https://gitlab.com/gitlab-org/gitlab/-/issues/214390
* https://gitlab.com/gitlab-org/gitlab/-/issues/215674

Update docs with same copy change we have inside the app

Removed references to Starter tier.

The developer page for Jenkins integration was not closely linked to
the user documentation.

Add more prominent crosslinks.
Revise subheadings with titles that violate the style guide.
Remove duplicated information, establishing the user doc as SSOT.
A few minor cleanups. Tried to keep it minimal.

Add words to exceptions list, wrap in code tags, or fix the problem.
Whatever's needed.