1
0
mirror of synced 2025-12-23 11:54:18 -05:00

Update and standardize unordered lists to be - (#37854)

This commit is contained in:
Grace Park
2023-06-16 13:57:24 -07:00
committed by GitHub
parent 23e491aea4
commit 90039fc985
297 changed files with 2170 additions and 2165 deletions

View File

@@ -35,7 +35,7 @@ shortTitle: Amazon S3 storage
Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps:
* Create your Amazon S3 bucket for storing data generated by workflow runs.
- Create your Amazon S3 bucket for storing data generated by workflow runs.
{% data reusables.actions.enterprise-common-prereqs %}
{% data reusables.actions.enterprise-oidc-prereqs %}
@@ -104,9 +104,9 @@ To configure {% data variables.product.prodname_ghe_server %} to use OIDC with a
1. Open the AWS Console, and navigate to the Identity and Access Management (IAM) service.
1. In the left menu, under "Access management", click **Roles**, then click **Create Role**.
1. On the "Select trusted entity" page, enter the following options:
* For "Trusted entity type", click **Web identity**.
* For "Identity provider", use the **Choose provider** drop-down menu and select the OIDC provider you created in the previous steps. It should be named `HOSTNAME/_services/token`, where `HOSTNAME` is the public hostname for {% data variables.location.product_location_enterprise %}.
* For "Audience", select `sts.amazonaws.com`.
- For "Trusted entity type", click **Web identity**.
- For "Identity provider", use the **Choose provider** drop-down menu and select the OIDC provider you created in the previous steps. It should be named `HOSTNAME/_services/token`, where `HOSTNAME` is the public hostname for {% data variables.location.product_location_enterprise %}.
- For "Audience", select `sts.amazonaws.com`.
1. Click **Next**.
1. On the "Add permissions" page, use the filter to find and select the `AmazonS3FullAccess` policy.
1. Click **Next**.
@@ -149,9 +149,9 @@ To configure {% data variables.product.prodname_ghe_server %} to use OIDC with a
{% data reusables.actions.enterprise-enable-checkbox %}
{% data reusables.actions.enterprise-s3-storage-setup %}
1. Under "Authentication", select **OpenID Connect (OIDC)**, and enter the values for your storage:
* **AWS S3 Bucket**: The name of your S3 bucket.
* **AWS Role**: The ARN for the role you created in the previous procedures. For example, `arn:aws:iam::123456789:role/my-role-name`.
* **AWS Region**: The AWS region for your bucket. For example, `us-east-1`.
- **AWS S3 Bucket**: The name of your S3 bucket.
- **AWS Role**: The ARN for the role you created in the previous procedures. For example, `arn:aws:iam::123456789:role/my-role-name`.
- **AWS Region**: The AWS region for your bucket. For example, `us-east-1`.
{% data reusables.enterprise_management_console.test-storage-button %}
{% data reusables.enterprise_management_console.save-settings %}

View File

@@ -27,15 +27,15 @@ shortTitle: Azure Blob storage
Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps:
* Create your Azure storage account for storing workflow data. {% data variables.product.prodname_actions %} stores its data as block blobs, and two storage account types are supported:
* A **general-purpose** storage account (also known as `general-purpose v1` or `general-purpose v2`) using the **standard** performance tier.
- Create your Azure storage account for storing workflow data. {% data variables.product.prodname_actions %} stores its data as block blobs, and two storage account types are supported:
- A **general-purpose** storage account (also known as `general-purpose v1` or `general-purpose v2`) using the **standard** performance tier.
{% warning %}
**Warning:** Using the **premium** performance tier with a general-purpose storage account is not supported. The **standard** performance tier must be selected when creating the storage account, and it cannot be changed later.
{% endwarning %}
* A **BlockBlobStorage** storage account, which uses the **premium** performance tier.
- A **BlockBlobStorage** storage account, which uses the **premium** performance tier.
For more information on Azure storage account types and performance tiers, see the [Azure documentation](https://docs.microsoft.com/en-us/azure/storage/common/storage-account-overview?toc=/azure/storage/blobs/toc.json#types-of-storage-accounts).
{% data reusables.actions.enterprise-common-prereqs %}
@@ -93,10 +93,10 @@ To configure {% data variables.product.prodname_ghe_server %} to use OIDC with a
{% data reusables.actions.enterprise-enable-checkbox %}
{% data reusables.actions.enterprise-azure-storage-setup %}
1. Under "Authentication", select **OpenID Connect (OIDC)**, and enter the values for your storage that you noted down in the previous procedures:
* Azure tenant ID
* Azure client ID
* Azure storage account name
* Azure blob endpoint suffix
- Azure tenant ID
- Azure client ID
- Azure storage account name
- Azure blob endpoint suffix
{% data reusables.enterprise_management_console.test-storage-button %}
{% data reusables.enterprise_management_console.save-settings %}

View File

@@ -31,7 +31,7 @@ shortTitle: Google Cloud Storage
Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps:
* Create your Google Cloud Storage bucket for storing data generated by workflow runs.
- Create your Google Cloud Storage bucket for storing data generated by workflow runs.
{% data reusables.actions.enterprise-common-prereqs %}
{% data reusables.actions.enterprise-oidc-prereqs %}
@@ -48,10 +48,10 @@ To configure {% data variables.product.prodname_ghe_server %} to use OIDC with G
When creating the service account, ensure that you do the following:
* Enable the IAM API as described at the start of [Creating and managing service accounts](https://cloud.google.com/iam/docs/creating-managing-service-accounts).
* Add the following roles to the service account:
* Service Account Token Creator
* Storage Object Admin
- Enable the IAM API as described at the start of [Creating and managing service accounts](https://cloud.google.com/iam/docs/creating-managing-service-accounts).
- Add the following roles to the service account:
- Service Account Token Creator
- Storage Object Admin
1. After creating the service account, note its email address, as it is need later. The service account email address is in the format `SERVICE-ACCOUNT-NAME@PROJECT-NAME.iam.gserviceaccount.com`.
### 2. Create an identity pool and identity provider
@@ -113,14 +113,14 @@ To configure {% data variables.product.prodname_ghe_server %} to use OIDC with G
{% data reusables.actions.enterprise-enable-checkbox %}
{% data reusables.actions.enterprise-gcp-storage-setup %}
1. Under "Authentication", select **OpenID Connect (OIDC)**, and enter the values for your storage:
* **Service URL**: The service URL for your bucket. This is usually `https://storage.googleapis.com`.
* **Bucket name**: The name of your bucket.
* **Workload Identity Provider ID**: The identity provider ID for your identity pool.
- **Service URL**: The service URL for your bucket. This is usually `https://storage.googleapis.com`.
- **Bucket name**: The name of your bucket.
- **Workload Identity Provider ID**: The identity provider ID for your identity pool.
This is in the format `projects/PROJECT-NUMBER/locations/global/workloadIdentityPools/POOL-NAME/providers/PROVIDER-NAME`. Note that you must remove the `https://iam.googleapis.com/` prefix from the value noted in the previous procedure.
For example, `projects/1234567890/locations/global/workloadIdentityPools/my-pool/providers/my-provider`.
* **Service account**: The service account email address that you noted in the previous procedure. For example, `ghes-oidc-service-account@my-project.iam.gserviceaccount.com`.
- **Service account**: The service account email address that you noted in the previous procedure. For example, `ghes-oidc-service-account@my-project.iam.gserviceaccount.com`.
{% data reusables.enterprise_management_console.test-storage-button %}
{% data reusables.enterprise_management_console.save-settings %}
@@ -132,15 +132,15 @@ To configure {% data variables.product.prodname_ghe_server %} to use OIDC with G
The service account must have the following [Identity and Access Management (IAM) permissions](https://cloud.google.com/storage/docs/access-control/iam-permissions) for the bucket:
* `storage.objects.create`
* `storage.objects.get`
* `storage.objects.list`
* `storage.objects.update`
* `storage.objects.delete`
* `storage.multipartUploads.create`
* `storage.multipartUploads.abort`
* `storage.multipartUploads.listParts`
* `storage.multipartUploads.list`
- `storage.objects.create`
- `storage.objects.get`
- `storage.objects.list`
- `storage.objects.update`
- `storage.objects.delete`
- `storage.multipartUploads.create`
- `storage.multipartUploads.abort`
- `storage.multipartUploads.listParts`
- `storage.multipartUploads.list`
{% data reusables.enterprise_site_admin_settings.access-settings %}
{% data reusables.enterprise_site_admin_settings.management-console %}
{% data reusables.enterprise_management_console.actions %}

View File

@@ -22,7 +22,7 @@ shortTitle: MinIO storage
Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps:
* Create your MinIO bucket for storing data generated by workflow runs. For more information about installing and configuring MinIO, see "[MinIO High Performance Object Storage](https://min.io/docs/minio/container/index.html)" and "[mc mb](https://min.io/docs/minio/linux/reference/minio-mc/mc-mb.html)" in the MinIO documentation.
- Create your MinIO bucket for storing data generated by workflow runs. For more information about installing and configuring MinIO, see "[MinIO High Performance Object Storage](https://min.io/docs/minio/container/index.html)" and "[mc mb](https://min.io/docs/minio/linux/reference/minio-mc/mc-mb.html)" in the MinIO documentation.
To avoid resource contention on the appliance, we recommend that MinIO be hosted separately from {% data variables.location.product_location %}.