Skip to content

Use correct praefect keys in reference arch docs

Robert Marshall requested to merge use-correct-praefect-keys-in-reference-arch-docs into master

What does this MR do?

- The praefect keys database_host_no_proxy and database_port_no_proxy
  were both deprecated in GitLab 14.0. The reference architecture
  documentation should reflect the updated keys database_direct_host and
  database_direct_port

Related https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/6039

Related https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/6150

Changelog: changed

Signed-off-by: Robert Marshall <rmarshall@gitlab.com>

Related issues

Related omnibus-gitlab#6039 (closed)

Related omnibus-gitlab#6150 (closed)

Author's checklist

If you are a GitLab team member and only adding documentation, do not add any of the following labels:

  • ~"frontend"
  • ~"backend"
  • ~"type::bug"
  • ~"database"

These labels cause the MR to be added to code verification QA issues.

Reviewer's checklist

Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.

  • If the content requires it, ensure the information is reviewed by a subject matter expert.
  • Technical writer review items:
    • Ensure docs metadata is present and up-to-date.
    • Ensure the appropriate labels are added to this MR.
    • Ensure a release milestone is set.
    • If relevant to this MR, ensure content topic type principles are in use, including:
      • The headings should be something you'd do a Google search for. Instead of Default behavior, say something like Default behavior when you close an issue.
      • The headings (other than the page title) should be active. Instead of Configuring GDK, say something like Configure GDK.
      • Any task steps should be written as a numbered list.
      • If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
  • Review by assigned maintainer, who can always request/require the reviews above. Maintainer's review can occur before or after a technical writer review.

Merge request reports