Add latest changes from gitlab-org/gitlab@master

This commit is contained in:
GitLab Bot 2022-08-24 06:10:06 +00:00
parent 6b3bc1ad35
commit ee3e134b76
10 changed files with 14 additions and 21 deletions

View File

@ -53,7 +53,7 @@ export default {
v-gl-tooltip.hover="showTooltipOnHover"
:name="iconName"
:title="workItemTooltipTitle"
class="gl-mr-2"
class="gl-mr-2 gl-text-gray-500"
/>
<span v-if="workItemTypeName" :class="{ 'gl-sr-only': !showText }">{{ workItemTypeName }}</span>
</span>

View File

@ -7,9 +7,6 @@ html {
}
body {
// Improves readability for dyslexic users; supported only in Chrome/Safari so far
text-decoration-skip: ink;
&.navless {
background-color: $white !important;
}

View File

@ -427,7 +427,8 @@
padding-inline-start: 28px;
margin-inline-start: 0 !important;
input.task-list-item-checkbox {
> p > input.task-list-item-checkbox,
> input.task-list-item-checkbox {
position: absolute;
inset-inline-start: $gl-padding-8;
inset-block-start: 5px;

View File

@ -591,9 +591,6 @@ svg {
html {
overflow-y: scroll;
}
body {
text-decoration-skip: ink;
}
.btn {
border-radius: 4px;
font-size: 0.875rem;

View File

@ -570,9 +570,6 @@ svg {
html {
overflow-y: scroll;
}
body {
text-decoration-skip: ink;
}
.btn {
border-radius: 4px;
font-size: 0.875rem;

View File

@ -338,9 +338,6 @@ hr {
html {
overflow-y: scroll;
}
body {
text-decoration-skip: ink;
}
body.navless {
background-color: #fff !important;
}

View File

@ -20,13 +20,13 @@ GitLab Dedicated enables you to offload the operational overhead of managing the
- Authentication: Support for instance-level [SAML OmniAuth](../../integration/saml.md) functionality. GitLab Dedicated acts as the service provider, and you must provide the necessary [configuration](../../integration/saml.md#general-setup) in order for GitLab to communicate with your IdP. This is provided during onboarding. SAML [request signing](../../integration/saml.md#request-signing-optional) is supported.
- Networking:
- Public connectivity
- Public connectivity with support for IP Allowlists. During onboarding, you can optionally specify a list of IP addresses that can access your Dedicated instance. Subsequently, when an IP not on the allowlist tries to access your instance the connection will be refused.
- Optional. Private connectivity via [AWS PrivateLink](https://aws.amazon.com/privatelink/).
You can specify an AWS IAM Principal and preferred Availability Zones during onboarding to enable this functionality.
- Upgrade strategy:
You can specify an AWS IAM Principal and preferred Availability Zones during onboarding to enable this functionality. Both Ingress and Egress Private Links are supported. When connecting to an internal service running in your VPC over https via PrivateLink, Dedicated supports the ability to use a private SSL certificate, which can be provided during onboarding.
- Upgrades:
- Monthly upgrades tracking one release behind the latest (n-1), with the latest security release.
- Out of band security patches provided for high severity releases.
- Backup strategy: regular backups taken and tested.
- Backups: regular backups taken and tested.
- Choice of cloud region: upon onboarding, choose the cloud region where you want to deploy your instance. Some AWS regions have limited features and as a result, we are not able to deploy production instances to those regions. See below for the [full list of regions](#aws-regions-not-supported) not currently supported.
- Security: Data encrypted at rest and in transit using latest encryption standards.
- Application: Self-managed [Ultimate feature set](https://about.gitlab.com/pricing/self-managed/feature-comparison/) with the exception of the unsupported features [listed below](#features-not-available-at-launch).

View File

@ -46,8 +46,6 @@ applies to:
You should consider some security implications before configuring IP address restrictions.
- Restricting HTTP traffic on GitLab.com with IP address restrictions causes SSH requests (including Git operations over
SSH) to fail. For more information, see [the relevant issue](https://gitlab.com/gitlab-org/gitlab/-/issues/271673).
- Administrators and group owners can access group settings from any IP address, regardless of IP restriction. However:
- Groups owners cannot access projects belonging to the group when accessing from a disallowed IP address.
- Administrators can access projects belonging to the group when accessing from a disallowed IP address.
@ -60,6 +58,8 @@ You should consider some security implications before configuring IP address res
restricted IP address, the IP restriction prevents code from being cloned.
- Users may still see some events from the IP restricted groups and projects on their dashboard. Activity may include
push, merge, issue, or comment events.
- IP access restrictions for Git operations via SSH are supported only on GitLab SaaS.
IP access restrictions applied to self-managed instances block SSH completely.
### Restrict group access by IP address

View File

@ -9,7 +9,7 @@
# There is a more opinionated template which we suggest the users to abide,
# which is the lib/gitlab/ci/templates/Terraform.gitlab-ci.yml
image:
name: "$CI_TEMPLATE_REGISTRY_HOST/gitlab-org/terraform-images/releases/terraform:1.1.9"
name: "$CI_TEMPLATE_REGISTRY_HOST/gitlab-org/terraform-images/releases/1.1:v0.43.0"
variables:
TF_ROOT: ${CI_PROJECT_DIR} # The relative path to the root directory of the Terraform project

View File

@ -50,6 +50,10 @@ describe('Work Item type component', () => {
expect(wrapper.text()).toBe(text);
});
it('renders the icon in gray color', () => {
expect(findIcon().classes()).toContain('gl-text-gray-500');
});
it('shows tooltip on hover when props passed', () => {
const tooltip = getBinding(findIcon().element, 'gl-tooltip');