diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2019-12-03 13:28:37 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2019-12-03 13:28:37 +0300 |
commit | 662bb2b6f1f5b5730a0d1eaa66238e718468645d (patch) | |
tree | c1ca759e7d2c96e9c2023bbcf946f79e423473a5 /doc | |
parent | ed8af41027110fdad8f7bb4d53329eb73417fb8d (diff) |
Add latest changes from gitlab-org/gitlab@12-5-stable-ee
Diffstat (limited to 'doc')
-rw-r--r-- | doc/administration/geo/replication/index.md | 8 | ||||
-rw-r--r-- | doc/administration/logs.md | 26 | ||||
-rw-r--r-- | doc/ci/environments.md | 5 | ||||
-rw-r--r-- | doc/ci/environments/environments_dashboard.md | 51 | ||||
-rw-r--r-- | doc/ci/environments/img/environments_dashboard_v12_5.png | bin | 0 -> 30989 bytes | |||
-rw-r--r-- | doc/ci/yaml/README.md | 45 | ||||
-rw-r--r-- | doc/integration/sourcegraph.md | 7 | ||||
-rw-r--r-- | doc/user/admin_area/settings/continuous_integration.md | 5 | ||||
-rw-r--r-- | doc/user/application_security/sast/analyzers.md | 2 | ||||
-rw-r--r-- | doc/user/application_security/sast/index.md | 1 | ||||
-rw-r--r-- | doc/user/application_security/security_dashboard/index.md | 2 | ||||
-rw-r--r-- | doc/user/clusters/applications.md | 12 | ||||
-rw-r--r-- | doc/user/group/epics/index.md | 23 | ||||
-rw-r--r-- | doc/user/operations_dashboard/index.md | 2 | ||||
-rw-r--r-- | doc/user/project/clusters/add_remove_clusters.md | 135 | ||||
-rw-r--r-- | doc/user/project/issues/issue_data_and_actions.md | 2 | ||||
-rw-r--r-- | doc/user/project/releases/index.md | 4 |
17 files changed, 239 insertions, 91 deletions
diff --git a/doc/administration/geo/replication/index.md b/doc/administration/geo/replication/index.md index 1fef2e85ce6..0d2ca9ea9d9 100644 --- a/doc/administration/geo/replication/index.md +++ b/doc/administration/geo/replication/index.md @@ -266,7 +266,7 @@ these epics/issues: | All database content | **Yes** | **Yes** | | | Project repository | **Yes** | **Yes** | | | Project wiki repository | **Yes** | **Yes** | | -| Project designs repository | [No][design-replication] | [No][design-verification] | | +| Project designs repository | **Yes** | [No][design-verification] | Behind feature flag (2) | | Uploads | **Yes** | [No][upload-verification] | Verified only on transfer, or manually (1) | | LFS Objects | **Yes** | [No][lfs-verification] | Verified only on transfer, or manually (1) | | CI job artifacts (other than traces) | **Yes** | [No][artifact-verification] | Verified only manually (1) | @@ -307,6 +307,12 @@ these epics/issues: 1. The integrity can be verified manually using [Integrity Check Rake Task](../../raketasks/check.md) on both nodes and comparing the output between them. +1. Enable the `enable_geo_design_sync` feature flag by running the +following in a Rails console: + + ```ruby + Feature.disable(:enable_geo_design_sync) + ``` DANGER: **DANGER** Features not on this list, or with **No** in the **Replicated** column, diff --git a/doc/administration/logs.md b/doc/administration/logs.md index aa10cdd220c..e1910b0b3f3 100644 --- a/doc/administration/logs.md +++ b/doc/administration/logs.md @@ -67,20 +67,18 @@ NOTE: **Note:** Starting with GitLab 12.5, if an error occurs, an "queue_duration": 274.35, "correlation_id": "KjDVUhNvvV3", "cpu_s": 2.837645135999999, - "exception": { - "class": "NameError", - "message": "undefined local variable or method `adsf' for #<Admin::DashboardController:0x00007ff3c9648588>", - "backtrace": [ - "app/controllers/admin/dashboard_controller.rb:11:in `index'", - "ee/app/controllers/ee/admin/dashboard_controller.rb:14:in `index'", - "ee/lib/gitlab/ip_address_state.rb:10:in `with'", - "ee/app/controllers/ee/application_controller.rb:43:in `set_current_ip_address'", - "lib/gitlab/session.rb:11:in `with_session'", - "app/controllers/application_controller.rb:450:in `set_session_storage'", - "app/controllers/application_controller.rb:444:in `set_locale'", - "ee/lib/gitlab/jira/middleware.rb:19:in `call'" - ] - } + "exception.class": "NameError", + "exception.message": "undefined local variable or method `adsf' for #<Admin::DashboardController:0x00007ff3c9648588>", + "exception.backtrace": [ + "app/controllers/admin/dashboard_controller.rb:11:in `index'", + "ee/app/controllers/ee/admin/dashboard_controller.rb:14:in `index'", + "ee/lib/gitlab/ip_address_state.rb:10:in `with'", + "ee/app/controllers/ee/application_controller.rb:43:in `set_current_ip_address'", + "lib/gitlab/session.rb:11:in `with_session'", + "app/controllers/application_controller.rb:450:in `set_session_storage'", + "app/controllers/application_controller.rb:444:in `set_locale'", + "ee/lib/gitlab/jira/middleware.rb:19:in `call'" + ] } ``` diff --git a/doc/ci/environments.md b/doc/ci/environments.md index 6d620722608..0f978a8f3a9 100644 --- a/doc/ci/environments.md +++ b/doc/ci/environments.md @@ -738,6 +738,11 @@ NOTE: **Note:** The most _specific_ spec takes precedence over the other wildcard matching. In this case, `review/feature-1` spec takes precedence over `review/*` and `*` specs. +### Environments Dashboard **(PREMIUM)** + +See [Environments Dashboard](environments/environments_dashboard.md) for a summary of each +environment's operational health. + ## Limitations In the `environment: name`, you are limited to only the [predefined environment variables](variables/predefined_variables.md). diff --git a/doc/ci/environments/environments_dashboard.md b/doc/ci/environments/environments_dashboard.md new file mode 100644 index 00000000000..f82728cd587 --- /dev/null +++ b/doc/ci/environments/environments_dashboard.md @@ -0,0 +1,51 @@ +--- +type: reference +--- + +# Environments Dashboard **(PREMIUM)** + +> [Introduced](https://gitlab.com/gitlab-org/gitlab/issues/3713) in [GitLab Premium](https://about.gitlab.com/pricing/) 12.5. + +The Environments Dashboard provides a cross-project +environment-based view that lets you see the big picture +of what is going on in each environment. From a single +location, you can track the progress as changes flow +from development to staging, and then to production (or +through any series of custom environment flows you can set up). +With an at-a-glance view of multiple projects, you can instantly +see which pipelines are green and which are red allowing you to +diagnose if there is a block at a particular point, or if there’s +a more systemic problem you need to investigate. + +You can access the dashboard from the top bar by clicking +**More > Environments**. + +![Environments Dashboard with projects](img/environments_dashboard_v12_5.png) + +The Environments Dashboard displays a maximum of 7 projects +and 3 environments per project. + +The listed environments for each project are unique, such as +"production", "staging", etc. Review apps and other grouped +environments are not displayed. + +## Adding a project to the dashboard + +To add a project to the dashboard: + +1. Click the **Add projects** button in the homescreen of the dashboard. +1. Search and add one or more projects using the **Search your projects** field. +1. Click the **Add projects** button. + +Once added, you can see a summary of each project's environment operational +health, including the latest commit, pipeline status, and deployment time. + +The Environments and [Operations](../../user/operations_dashboard/index.md) +dashboards share the same list of projects. When you add or remove a +project from one, GitLab adds or removes the project from the other. + +## Environment dashboards on GitLab.com + +GitLab.com users can add public projects to the Environments +Dashboard for free. If your project is private, the group it belongs +to must have a [GitLab Silver](https://about.gitlab.com/pricing/) plan. diff --git a/doc/ci/environments/img/environments_dashboard_v12_5.png b/doc/ci/environments/img/environments_dashboard_v12_5.png Binary files differnew file mode 100644 index 00000000000..e83c4fac75b --- /dev/null +++ b/doc/ci/environments/img/environments_dashboard_v12_5.png diff --git a/doc/ci/yaml/README.md b/doc/ci/yaml/README.md index 62644e78872..73e976a6145 100644 --- a/doc/ci/yaml/README.md +++ b/doc/ci/yaml/README.md @@ -1539,9 +1539,14 @@ cache: > [Introduced](https://gitlab.com/gitlab-org/gitlab/issues/18986) in GitLab v12.5. -If `cache:key:files` is added, one or two files must be defined with it. The cache `key` -will be a SHA computed from the most recent commits (one or two) that changed the -given files. If neither file was changed in any commits, the key will be `default`. +The `cache:key:files` keyword extends the `cache:key` functionality by making it easier +to reuse some caches, and rebuild them less often, which will speed up subsequent pipeline +runs. + +When you include `cache:key:files`, you must also list the project files that will be used to generate the key, up to a maximum of two files. +The cache `key` will be a SHA checksum computed from the most recent commits (up to two, if two files are listed) +that changed the given files. If neither file was changed in any commits, +the fallback key will be `default`. ```yaml cache: @@ -1554,20 +1559,26 @@ cache: - node_modules ``` +In this example we are creating a cache for Ruby and Nodejs dependencies that +is tied to current versions of the `Gemfile.lock` and `package.json` files. Whenever one of +these files changes, a new cache key is computed and a new cache is created. Any future +job runs using the same `Gemfile.lock` and `package.json` with `cache:key:files` will +use the new cache, instead of rebuilding the dependencies. + ##### `cache:key:prefix` > [Introduced](https://gitlab.com/gitlab-org/gitlab/issues/18986) in GitLab v12.5. - The `prefix` parameter adds extra functionality to `key:files` by allowing the key to be composed of the given `prefix` combined with the SHA computed for `cache:key:files`. -For example, adding a `prefix` of `rspec`, will -cause keys to look like: `rspec-feef9576d21ee9b6a32e30c5c79d0a0ceb68d1e5`. If neither -file was changed in any commits, the prefix is added to `default`, so the key in the -example would be `rspec-default`. +For example, adding a `prefix` of `test`, will cause keys to look like: `test-feef9576d21ee9b6a32e30c5c79d0a0ceb68d1e5`. +If neither file was changed in any commits, the prefix is added to `default`, so the +key in the example would be `test-default`. -`prefix` follows the same restrictions as `key`, so it can use any of the -[predefined variables](../variables/README.md). Similarly, the `/` character or the -equivalent URI-encoded `%2F`, or a value made only of `.` or `%2E`, is not allowed. +Like `cache:key`, `prefix` can use any of the [predefined variables](../variables/README.md), +but the following are not allowed: + +- the `/` character (or the equivalent URI-encoded `%2F`) +- a value made only of `.` (or the equivalent URI-encoded `%2E`) ```yaml cache: @@ -1577,8 +1588,20 @@ cache: prefix: ${CI_JOB_NAME} paths: - vendor/ruby + +rspec: + script: + - bundle exec rspec ``` +For example, adding a `prefix` of `$CI_JOB_NAME` will +cause the key to look like: `rspec-feef9576d21ee9b6a32e30c5c79d0a0ceb68d1e5` and +the job cache is shared across different branches. If a branch changes +`Gemfile.lock`, that branch will have a new SHA checksum for `cache:key:files`. A new cache key +will be generated, and a new cache will be created for that key. +If `Gemfile.lock` is not found, the prefix is added to +`default`, so the key in the example would be `rspec-default`. + #### `cache:untracked` Set `untracked: true` to cache all files that are untracked in your Git diff --git a/doc/integration/sourcegraph.md b/doc/integration/sourcegraph.md index 5e7cbdfbac3..358657ca172 100644 --- a/doc/integration/sourcegraph.md +++ b/doc/integration/sourcegraph.md @@ -108,9 +108,10 @@ When visiting one of these views, you can now hover over a code reference to see Sourcegraph powered code intelligence will be incrementally rolled out on GitLab.com. It will eventually become available for all public projects, but for now, it is only -available for some specific [`gitlab-org` projects](https://gitlab.com/gitlab-org/). -This means that you can see it working and use it to dig into the code of these projects, -but you cannot use it on your own project on GitLab.com yet. +available for some specific projects within the [`gitlab-org`](https://gitlab.com/gitlab-org/) +group, e.g., <https://gitlab.com/gitlab-org/gitlab>. This means that you can see +it working and use it to dig into the code of these projects, but you cannot use +it on your own project on GitLab.com yet. If you would like to use it in your own projects as of GitLab 12.5, you can do so by setting up a self-managed GitLab instance. diff --git a/doc/user/admin_area/settings/continuous_integration.md b/doc/user/admin_area/settings/continuous_integration.md index f775dd8bbb4..79deda73d34 100644 --- a/doc/user/admin_area/settings/continuous_integration.md +++ b/doc/user/admin_area/settings/continuous_integration.md @@ -161,6 +161,11 @@ but commented out to help encourage others to add to it in the future. --> ## Required pipeline configuration **(PREMIUM ONLY)** +CAUTION: **Caution:** +The Required Pipeline Configuration feature is deprecated and will be removed when an +[improved compliance solution](https://gitlab.com/gitlab-org/gitlab/issues/34830) +is added to GitLab. It is recommended to avoid using this feature. + GitLab administrators can force a pipeline configuration to run on every pipeline. diff --git a/doc/user/application_security/sast/analyzers.md b/doc/user/application_security/sast/analyzers.md index 6eb2ca71e71..b79edc9d5a8 100644 --- a/doc/user/application_security/sast/analyzers.md +++ b/doc/user/application_security/sast/analyzers.md @@ -15,7 +15,7 @@ SAST supports the following official analyzers: - [`bandit`](https://gitlab.com/gitlab-org/security-products/analyzers/bandit) (Bandit) - [`brakeman`](https://gitlab.com/gitlab-org/security-products/analyzers/brakeman) (Brakeman) -- [`eslint`](https://gitlab.com/gitlab-org/security-products/analyzers/eslint) (ESLint (JavaScript)) +- [`eslint`](https://gitlab.com/gitlab-org/security-products/analyzers/eslint) (ESLint (JavaScript and React)) - [`flawfinder`](https://gitlab.com/gitlab-org/security-products/analyzers/flawfinder) (Flawfinder) - [`gosec`](https://gitlab.com/gitlab-org/security-products/analyzers/gosec) (Gosec) - [`nodejs-scan`](https://gitlab.com/gitlab-org/security-products/analyzers/nodejs-scan) (NodeJsScan) diff --git a/doc/user/application_security/sast/index.md b/doc/user/application_security/sast/index.md index 615eb072ea7..f427f33c8c2 100644 --- a/doc/user/application_security/sast/index.md +++ b/doc/user/application_security/sast/index.md @@ -76,6 +76,7 @@ The following table shows which languages, package managers and frameworks are s | Node.js | [NodeJsScan](https://github.com/ajinabraham/NodeJsScan) | 11.1 | | PHP | [phpcs-security-audit](https://github.com/FloeDesignTechnologies/phpcs-security-audit) | 10.8 | | Python ([pip](https://pip.pypa.io/en/stable/)) | [bandit](https://github.com/PyCQA/bandit) | 10.3 | +| React | [ESLint react plugin](https://github.com/yannickcr/eslint-plugin-react) | 12.5 | | Ruby on Rails | [brakeman](https://brakemanscanner.org) | 10.3 | | Scala ([Ant](https://ant.apache.org/), [Gradle](https://gradle.org/), [Maven](https://maven.apache.org/) and [SBT](https://www.scala-sbt.org/)) | [SpotBugs](https://spotbugs.github.io/) with the [find-sec-bugs](https://find-sec-bugs.github.io/) plugin | 11.0 (SBT) & 11.9 (Ant, Gradle, Maven) | | TypeScript | [TSLint config security](https://github.com/webschik/tslint-config-security/) | 11.9 | diff --git a/doc/user/application_security/security_dashboard/index.md b/doc/user/application_security/security_dashboard/index.md index 688d231d568..7eb0d649648 100644 --- a/doc/user/application_security/security_dashboard/index.md +++ b/doc/user/application_security/security_dashboard/index.md @@ -71,7 +71,7 @@ Once you're on the dashboard, at the top you should see a series of filters for: - Report type - Project -To the right of the filters, you should see a **Hide dismissed** toggle button ([available in GitLab Ultimate 12.5](https://gitlab.com/gitlab-org/gitlab/issues/9102)). +To the right of the filters, you should see a **Hide dismissed** toggle button ([available for GitLab.com Gold, planned for GitLab Ultimate 12.6](https://gitlab.com/gitlab-org/gitlab/issues/9102)). NOTE: **Note:** The dashboard only shows projects with [security reports](#supported-reports) enabled in a group. diff --git a/doc/user/clusters/applications.md b/doc/user/clusters/applications.md index c3e2e6bca5b..7ee1650f698 100644 --- a/doc/user/clusters/applications.md +++ b/doc/user/clusters/applications.md @@ -417,6 +417,18 @@ install Crossplane using the [`values.yaml`](https://github.com/crossplaneio/crossplane/blob/master/cluster/charts/crossplane/values.yaml.tmpl) file. +#### Enabling installation + +This is a preliminary release of Crossplane as a GitLab-managed application. By default, +the ability to install it is disabled. + +To allow installation of Crossplane as a GitLab-managed application, ask a GitLab +administrator to run following command within a Rails console: + +```ruby +Feature.enable(:enable_cluster_application_crossplane) +``` + ## Upgrading applications > [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/merge_requests/24789) in GitLab 11.8. diff --git a/doc/user/group/epics/index.md b/doc/user/group/epics/index.md index 0753df70bc2..01e277d5559 100644 --- a/doc/user/group/epics/index.md +++ b/doc/user/group/epics/index.md @@ -50,14 +50,17 @@ Any issue that belongs to a project in the epic's group, or any of the epic's subgroups, are eligible to be added. New issues appear at the top of the list of issues in the **Epics and Issues** tab. An epic contains a list of issues and an issue can be associated with at most -one epic. When you add an issue to an epic that is already associated with another epic, -the issue is automatically removed from the previous epic. +one epic. When you add an issue that is already linked to an epic, +the issue is automatically unlinked from its current parent. To add an issue to an epic: 1. Click **Add an issue**. -1. Paste the link of the issue. - - Press <kbd>Spacebar</kbd> and repeat this step if there are multiple issues. +1. Identify the issue to be added, using either of the following methods: + - Paste the link of the issue. + - Search for the desired issue by entering part of the issue's title, then selecting the desired match. ([From GitLab 12.5](https://gitlab.com/gitlab-org/gitlab/issues/9126)) + + If there are multiple issues to be added, press <kbd>Spacebar</kbd> and repeat this step. 1. Click **Add**. To remove an issue from an epic: @@ -72,17 +75,19 @@ To remove an issue from an epic: Any epic that belongs to a group, or subgroup of the parent epic's group, is eligible to be added. New child epics appear at the top of the list of epics in the **Epics and Issues** tab. -When you add a child epic that is already associated with another epic, -that epic is automatically removed from the previous epic. +When you add an epic that is already linked to a parent epic, the link to its current parent is removed. An epic can have multiple child epics with the maximum depth being 5. -To add a child epic: +To add a child epic to an epic: 1. Click **Add an epic**. -1. Paste the link of the epic. - - Press <kbd>Spacebar</kbd> and repeat this step if there are multiple issues. +1. Identify the epic to be added, using either of the following methods: + - Paste the link of the epic. + - Search for the desired issue by entering part of the epic's title, then selecting the desired match. ([From GitLab 12.5](https://gitlab.com/gitlab-org/gitlab/issues/9126)) + + If there are multiple epics to be added, press <kbd>Spacebar</kbd> and repeat this step. 1. Click **Add**. To remove a child epic from a parent epic: diff --git a/doc/user/operations_dashboard/index.md b/doc/user/operations_dashboard/index.md index cdb80cca6f7..531422ca077 100644 --- a/doc/user/operations_dashboard/index.md +++ b/doc/user/operations_dashboard/index.md @@ -23,6 +23,8 @@ To add a project to the dashboard: Once added, the dashboard will display the project's number of active alerts, last commit, pipeline status, and when it was last deployed. +The Operations and [Environments](../../ci/environments/environments_dashboard.md) dashboards share the same list of projects. Adding or removing a project from one adds or removes the project from the other. + ![Operations Dashboard with projects](img/index_operations_dashboard_with_projects.png) ## Arranging projects on a dashboard diff --git a/doc/user/project/clusters/add_remove_clusters.md b/doc/user/project/clusters/add_remove_clusters.md index 150a451dfe5..c73368fbbd2 100644 --- a/doc/user/project/clusters/add_remove_clusters.md +++ b/doc/user/project/clusters/add_remove_clusters.md @@ -206,9 +206,46 @@ GitLab supports: Before creating your first cluster on Amazon EKS with GitLab's integration, make sure the following requirements are met: +- Enable the `create_eks_clusters` feature flag for your GitLab instance. - An [Amazon Web Services](https://aws.amazon.com/) account is set up and you are able to log in. - You have permissions to manage IAM resources. +#### Enable the `create_eks_clusters` feature flag **(CORE ONLY)** + +NOTE: **Note:** +If you are running a self-managed instance, EKS cluster creation will not be available +unless the feature flag `create_eks_clusters` is enabled. This can be done from the Rails console +by instance administrators. + +Use these commands to start the Rails console: + +```sh +# Omnibus GitLab +gitlab-rails console + +# Installation from source +cd /home/git/gitlab +sudo -u git -H bin/rails console RAILS_ENV=production +``` + +Then run the following command to enable the feature flag: + +``` +Feature.enable(:create_eks_clusters) +``` + +You can also enable the feature flag only for specific projects with: + +``` +Feature.enable(:create_eks_clusters, Project.find_by_full_path('my_group/my_project')) +``` + +Run the following command to disable the feature flag: + +``` +Feature.disable(:create_eks_clusters) +``` + ##### Additional requirements for self-managed instances If you are using a self-managed GitLab instance, GitLab must first @@ -262,55 +299,55 @@ new Kubernetes cluster to your project: 1. Click **Create Policy**, which will open a new window. 1. Select the **JSON** tab, and paste in the following snippet in place of the existing content: - ```json - { - "Version": "2012-10-17", - "Statement": [ - { - "Effect": "Allow", - "Action": [ - "autoscaling:CreateAutoScalingGroup", - "autoscaling:DescribeAutoScalingGroups", - "autoscaling:DescribeScalingActivities", - "autoscaling:UpdateAutoScalingGroup", - "autoscaling:CreateLaunchConfiguration", - "autoscaling:DescribeLaunchConfigurations", - "cloudformation:CreateStack", - "cloudformation:DescribeStacks", - "ec2:AuthorizeSecurityGroupEgress", - "ec2:AuthorizeSecurityGroupIngress", - "ec2:RevokeSecurityGroupEgress", - "ec2:RevokeSecurityGroupIngress", - "ec2:CreateSecurityGroup", - "ec2:createTags", - "ec2:DescribeImages", - "ec2:DescribeKeyPairs", - "ec2:DescribeRegions", - "ec2:DescribeSecurityGroups", - "ec2:DescribeSubnets", - "ec2:DescribeVpcs", - "eks:CreateCluster", - "eks:DescribeCluster", - "iam:AddRoleToInstanceProfile", - "iam:AttachRolePolicy", - "iam:CreateRole", - "iam:CreateInstanceProfile", - "iam:GetRole", - "iam:ListRoles", - "iam:PassRole", - "ssm:GetParameters" - ], - "Resource": "*" - } - ] - } - ``` - - NOTE: **Note:** - These permissions give GitLab the ability to create resources, but not delete them. - This means that if an error is encountered during the creation process, changes will - not be rolled back and you must remove resources manually. You can do this by deleting - the relevant [CloudFormation stack](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cfn-console-delete-stack.html) + ```json + { + "Version": "2012-10-17", + "Statement": [ + { + "Effect": "Allow", + "Action": [ + "autoscaling:CreateAutoScalingGroup", + "autoscaling:DescribeAutoScalingGroups", + "autoscaling:DescribeScalingActivities", + "autoscaling:UpdateAutoScalingGroup", + "autoscaling:CreateLaunchConfiguration", + "autoscaling:DescribeLaunchConfigurations", + "cloudformation:CreateStack", + "cloudformation:DescribeStacks", + "ec2:AuthorizeSecurityGroupEgress", + "ec2:AuthorizeSecurityGroupIngress", + "ec2:RevokeSecurityGroupEgress", + "ec2:RevokeSecurityGroupIngress", + "ec2:CreateSecurityGroup", + "ec2:createTags", + "ec2:DescribeImages", + "ec2:DescribeKeyPairs", + "ec2:DescribeRegions", + "ec2:DescribeSecurityGroups", + "ec2:DescribeSubnets", + "ec2:DescribeVpcs", + "eks:CreateCluster", + "eks:DescribeCluster", + "iam:AddRoleToInstanceProfile", + "iam:AttachRolePolicy", + "iam:CreateRole", + "iam:CreateInstanceProfile", + "iam:GetRole", + "iam:ListRoles", + "iam:PassRole", + "ssm:GetParameters" + ], + "Resource": "*" + } + ] + } + ``` + + NOTE: **Note:** + These permissions give GitLab the ability to create resources, but not delete them. + This means that if an error is encountered during the creation process, changes will + not be rolled back and you must remove resources manually. You can do this by deleting + the relevant [CloudFormation stack](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cfn-console-delete-stack.html) 1. Click **Review policy**. 1. Enter a suitable name for this policy, and click **Create Policy**. You can now close this window. diff --git a/doc/user/project/issues/issue_data_and_actions.md b/doc/user/project/issues/issue_data_and_actions.md index 92da4235afa..18f91352910 100644 --- a/doc/user/project/issues/issue_data_and_actions.md +++ b/doc/user/project/issues/issue_data_and_actions.md @@ -157,6 +157,8 @@ The plain text title and description of the issue fill the top center of the iss The description fully supports [GitLab Flavored Markdown](../../markdown.md#gitlab-flavored-markdown-gfm), allowing many formatting options. +> [Since GitLab 12.5](https://gitlab.com/gitlab-org/gitlab/issues/10103), changes to an issue's description are listed in the [issue history](#23-issue-history).**(STARTER)** + #### 17. Mentions You can mention a user or a group present in your GitLab instance with `@username` or diff --git a/doc/user/project/releases/index.md b/doc/user/project/releases/index.md index 8372aefc94c..9b7b20be98f 100644 --- a/doc/user/project/releases/index.md +++ b/doc/user/project/releases/index.md @@ -147,7 +147,7 @@ You can also edit an existing tag to add release notes: ## Release Evidence -> [Introduced](https://gitlab.com/gitlab-org/gitlab/issues/26019) in GitLab 12.5. +> [Introduced](https://gitlab.com/gitlab-org/gitlab/issues/26019) in GitLab 12.6. Each time a new release is created, specific related data is collected in parallel. This dataset will be a snapshot this new release (including linked @@ -155,7 +155,7 @@ milestones and issues) at moment of creation. Such collection of data will provide a chain of custody and facilitate processes like external audits, for example. The gathered Evidence data is stored in the database upon creation of a new -release as a JSON object. In GitLab 12.5, a link to +release as a JSON object. In GitLab 12.6, a link to the Evidence data is provided for [each Release](#releases-list). Here's what this object can look like: |