You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- title: 'Embedding Grafana panels in Markdown is deprecated'
2
+
announcement_milestone: '15.9'
3
+
removal_milestone: '16.0'
4
+
breaking_change: true
5
+
reporter: abellucci
6
+
body: |
7
+
The ability to add Grafana panels in GitLab Flavored Markdown is deprecated in 15.9 and will be removed in 16.0.
8
+
We intend to replace this feature with the ability to [embed charts](https://gitlab.com/groups/gitlab-org/opstrace/-/epics/33) with the [GitLab Observability UI](https://gitlab.com/gitlab-org/opstrace/opstrace-ui).
Copy file name to clipboardexpand all lines: db/structure.sql
+9
Original file line number
Diff line number
Diff line change
@@ -28624,6 +28624,8 @@ CREATE INDEX idx_packages_debian_group_component_files_on_architecture_id ON pac
28624
28624
28625
28625
CREATE INDEX idx_packages_debian_project_component_files_on_architecture_id ON packages_debian_project_component_files USING btree (architecture_id);
28626
28626
28627
+
CREATE INDEX idx_packages_on_project_id_name_id_version_when_installable_npm ON packages_packages USING btree (project_id, name, id, version) WHERE ((package_type = 2) AND (status = ANY (ARRAY[0, 1])));
28628
+
28627
28629
CREATE UNIQUE INDEX idx_packages_on_project_id_name_version_unique_when_generic ON packages_packages USING btree (project_id, name, version) WHERE ((package_type = 7) AND (status <> 4));
28628
28630
28629
28631
CREATE UNIQUE INDEX idx_packages_on_project_id_name_version_unique_when_golang ON packages_packages USING btree (project_id, name, version) WHERE ((package_type = 8) AND (status <> 4));
@@ -29002,6 +29004,8 @@ CREATE UNIQUE INDEX index_chat_teams_on_namespace_id ON chat_teams USING btree (
29002
29004
29003
29005
CREATE UNIQUE INDEX index_ci_build_needs_on_build_id_and_name ON ci_build_needs USING btree (build_id, name);
29004
29006
29007
+
CREATE INDEX index_ci_build_needs_on_partition_id_build_id ON ci_build_needs USING btree (partition_id, build_id);
29008
+
29005
29009
CREATE UNIQUE INDEX index_ci_build_pending_states_on_build_id ON ci_build_pending_states USING btree (build_id);
29006
29010
29007
29011
CREATE INDEX index_ci_build_pending_states_on_partition_id_build_id ON ci_build_pending_states USING btree (partition_id, build_id);
@@ -29900,6 +29904,8 @@ CREATE INDEX index_gitlab_subscriptions_on_max_seats_used_changed_at ON gitlab_s
29900
29904
29901
29905
CREATE UNIQUE INDEX index_gitlab_subscriptions_on_namespace_id ON gitlab_subscriptions USING btree (namespace_id);
29902
29906
29907
+
CREATE INDEX index_gitlab_subscriptions_on_trial_and_trial_starts_on ON gitlab_subscriptions USING btree (trial, trial_starts_on);
29908
+
29903
29909
CREATE UNIQUE INDEX index_gpg_key_subkeys_on_fingerprint ON gpg_key_subkeys USING btree (fingerprint);
29904
29910
29905
29911
CREATE INDEX index_gpg_key_subkeys_on_gpg_key_id ON gpg_key_subkeys USING btree (gpg_key_id);
@@ -34856,6 +34862,9 @@ ALTER TABLE ONLY chat_teams
Copy file name to clipboardexpand all lines: doc/administration/load_balancer.md
+3
Original file line number
Diff line number
Diff line change
@@ -115,6 +115,9 @@ Configure DNS for an alternate SSH hostname such as `altssh.gitlab.example.com`.
115
115
116
116
It is strongly recommend that multi-node deployments configure load balancers to use the [readiness check](../user/admin_area/monitoring/health_check.md#readiness) to ensure a node is ready to accept traffic, before routing traffic to it. This is especially important when utilizing Puma, as there is a brief period during a restart where Puma doesn't accept requests.
117
117
118
+
WARNING:
119
+
Using the `all=1` parameter with the readiness check in GitLab versions 15.4 to 15.8 may cause [increased Praefect memory usage](https://gitlab.com/gitlab-org/gitaly/-/issues/4751) and lead to memory errors.
120
+
118
121
## Troubleshooting
119
122
120
123
### The health check is returning a `408` HTTP code via the load balancer
If GitLab is [configured to use an Internet proxy](https://docs.gitlab.com/omnibus/settings/environment-variables.html), the endpoint IP
920
+
address must be added to the `no_proxy` list.
921
+
917
922
#### Encrypted S3 buckets
918
923
919
924
> - [Introduced](https://gitlab.com/gitlab-org/gitlab-workhorse/-/merge_requests/466) in GitLab 13.1 for instance profiles only and [S3 default encryption](https://docs.aws.amazon.com/AmazonS3/latest/dev/bucket-encryption.html).
Copy file name to clipboardexpand all lines: doc/architecture/blueprints/work_items/index.md
+16
Original file line number
Diff line number
Diff line change
@@ -70,6 +70,22 @@ All Work Item types share the same pool of predefined widgets and are customized
70
70
71
71
\* status is not currently a widget, but a part of the root work item, similar to title
72
72
73
+
### Work item relationships
74
+
75
+
Work items can be related to other work items in a number of different ways:
76
+
77
+
- Parent: A direct ancestor to the current work item, whose completion relies on completing this work item.
78
+
- Child: A direct descendant of the current work item, which contributes to this work item's completion.
79
+
- Blocked by: A work item preventing the completion of the current work item.
80
+
- Blocks: A work item whose completion is blocked by the current work item.
81
+
- Related: A work item that is relevant to the subject of the current work item, but does not directly contribute to or block the completion of this work item.
82
+
83
+
#### Hierarchy
84
+
85
+
Parent-child relationships form the basis of **hierarchy** in work items. Each work item type has a defined set of types that can be parents or children of that type.
86
+
87
+
As types expand, and parent items have their own parent items, the hierarchy capability can grow exponentially.
88
+
73
89
### Work Item view
74
90
75
91
The new frontend view that renders Work Items of any type using global Work Item `id` as an identifier.
Copy file name to clipboardexpand all lines: doc/ci/cloud_services/aws/index.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ group: Pipeline Authoring
4
4
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
5
5
---
6
6
7
-
# Configure OpenID Connect in AWS to retrieve temporary credentials
7
+
# Configure OpenID Connect in AWS to retrieve temporary credentials**(FREE)**
8
8
9
9
In this tutorial, we'll show you how to use a GitLab CI/CD job with a JSON web token (JWT) to retrieve temporary credentials from AWS without needing to store secrets.
10
10
To do this, you must configure OpenID Connect (OIDC) for ID federation between GitLab and AWS. For background and requirements for integrating GitLab using OIDC, see [Connect to cloud services](../index.md).
Copy file name to clipboardexpand all lines: doc/ci/cloud_services/azure/index.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ group: Pipeline Authoring
4
4
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
5
5
---
6
6
7
-
# Configure OpenID Connect in Azure to retrieve temporary credentials
7
+
# Configure OpenID Connect in Azure to retrieve temporary credentials**(FREE)**
8
8
9
9
This tutorial demonstrates how to use a JSON web token (JWT) in a GitLab CI/CD job
10
10
to retrieve temporary credentials from Azure without needing to store secrets.
Copy file name to clipboardexpand all lines: doc/ci/cloud_services/google_cloud/index.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ group: Pipeline Authoring
4
4
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
5
5
---
6
6
7
-
# Configure OpenID Connect with GCP Workload Identity Federation
7
+
# Configure OpenID Connect with GCP Workload Identity Federation**(FREE)**
8
8
9
9
WARNING:
10
10
The `CI_JOB_JWT_V2` variable is under development [(alpha)](../../../policy/alpha-beta-support.md#alpha-features) and is not yet suitable for production use.
0 commit comments