Skip to content

Commit 48feb73

Browse files
author
Martin Lopes
authored
[October 25, 2021] OpenID Connect - guides shipping on Oct 25 (#22392)
1 parent 1a30075 commit 48feb73

27 files changed

Lines changed: 681 additions & 9 deletions

‎assets/images/help/images/oidc-architecture.png‎

92.7 KB
Loading

content/actions/deployment/about-continuous-deployment.md renamed to content/actions/deployment/about-deployments/about-continuous-deployment.md

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,9 +7,11 @@ versions:
77
ghae: '*'
88
ghec: '*'
99
type: overview
10+
redirect_from:
11+
- /actions/deployment/about-continuous-deployment
1012
topics:
1113
- CD
12-
shortTitle: Continuous deployment
14+
shortTitle: About continuous deployment
1315
---
1416

1517
{% data reusables.actions.enterprise-beta %}
@@ -31,6 +33,14 @@ You can configure your CD workflow to run when a {% data variables.product.produ
3133
{% ifversion fpt or ghae or ghes > 3.0 or ghec %}
3234
{% data variables.product.prodname_actions %} provides features that give you more control over deployments. For example, you can use environments to require approval for a job to proceed, restrict which branches can trigger a workflow, or limit access to secrets. {% ifversion fpt or ghae-next or ghes > 3.1 or ghec %}You can use concurrency to limit your CD pipeline to a maximum of one in-progress deployment and one pending deployment. {% endif %}For more information about these features, see "[Deploying with GitHub Actions](/actions/deployment/deploying-with-github-actions)" and "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)."{% endif %}
3335

36+
{% ifversion fpt or ghec or ghae-issue-4856 %}
37+
38+
## Using OpenID Connect to access cloud resources
39+
40+
{% data reusables.actions.about-oidc-short-overview %}
41+
42+
{% endif %}
43+
3444
## Workflow templates and third party actions
3545

3646
{% data reusables.actions.cd-templates-actions %}

content/actions/deployment/deploying-with-github-actions.md renamed to content/actions/deployment/about-deployments/deploying-with-github-actions.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,8 @@ versions:
77
ghae: '*'
88
ghec: '*'
99
type: overview
10+
redirect_from:
11+
- /actions/deployment/deploying-with-github-actions
1012
topics:
1113
- CD
1214
shortTitle: Deploy with GitHub Actions

‎content/actions/deployment/about-deployments/index.md‎

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
---
2+
title: About deployments
3+
shortTitle: About deployments
4+
intro: 'Learn how deployments can run with {% data variables.product.prodname_actions %} workflows.'
5+
versions:
6+
fpt: '*'
7+
ghae: 'issue-4856'
8+
ghec: '*'
9+
children:
10+
- /about-continuous-deployment
11+
- /deploying-with-github-actions
12+
---

content/actions/deployment/deploying-to-amazon-elastic-container-service.md renamed to content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,7 @@ title: Deploying to Amazon Elastic Container Service
33
intro: You can deploy to Amazon Elastic Container Service (ECS) as part of your continuous deployment (CD) workflows.
44
redirect_from:
55
- /actions/guides/deploying-to-amazon-elastic-container-service
6+
- /actions/deployment/deploying-to-amazon-elastic-container-service
67
versions:
78
fpt: '*'
89
ghes: '*'
@@ -26,6 +27,16 @@ This guide explains how to use {% data variables.product.prodname_actions %} to
2627

2728
On every new push to `main` in your {% data variables.product.company_short %} repository, the {% data variables.product.prodname_actions %} workflow builds and pushes a new container image to Amazon ECR, and then deploys a new task definition to Amazon ECS.
2829

30+
{% ifversion fpt or ghec or ghae-issue-4856 %}
31+
32+
{% note %}
33+
34+
**Note**: {% data reusables.actions.about-oidc-short-overview %}
35+
36+
{% endnote %}
37+
38+
{% endif %}
39+
2940
## Prerequisites
3041

3142
Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps for Amazon ECR and ECS:

content/actions/deployment/deploying-to-azure-app-service.md renamed to content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure-app-service.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,7 @@ title: Deploying to Azure App Service
33
intro: You can deploy to Azure App Service as part of your continuous deployment (CD) workflows.
44
redirect_from:
55
- /actions/guides/deploying-to-azure-app-service
6+
- /actions/deployment/deploying-to-azure-app-service
67
versions:
78
fpt: '*'
89
ghes: '*'
@@ -26,6 +27,16 @@ This guide explains how to use {% data variables.product.prodname_actions %} to
2627

2728
Azure App Service can run web apps in several languages, but this guide demonstrates deploying an existing Node.js project.
2829

30+
{% ifversion fpt or ghec or ghae-issue-4856 %}
31+
32+
{% note %}
33+
34+
**Note**: {% data reusables.actions.about-oidc-short-overview %}
35+
36+
{% endnote %}
37+
38+
{% endif %}
39+
2940
## Prerequisites
3041

3142
Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps:

content/actions/deployment/deploying-to-google-kubernetes-engine.md renamed to content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,7 @@ title: Deploying to Google Kubernetes Engine
33
intro: You can deploy to Google Kubernetes Engine as part of your continuous deployment (CD) workflows.
44
redirect_from:
55
- /actions/guides/deploying-to-google-kubernetes-engine
6+
- /actions/deployment/deploying-to-google-kubernetes-engine
67
versions:
78
fpt: '*'
89
ghes: '*'
@@ -26,6 +27,16 @@ This guide explains how to use {% data variables.product.prodname_actions %} to
2627

2728
GKE is a managed Kubernetes cluster service from Google Cloud that can host your containerized workloads in the cloud or in your own datacenter. For more information, see [Google Kubernetes Engine](https://cloud.google.com/kubernetes-engine).
2829

30+
{% ifversion fpt or ghec or ghae-issue-4856 %}
31+
32+
{% note %}
33+
34+
**Note**: {% data reusables.actions.about-oidc-short-overview %}
35+
36+
{% endnote %}
37+
38+
{% endif %}
39+
2940
## Prerequisites
3041

3142
Before you proceed with creating the workflow, you will need to complete the following steps for your Kubernetes project. This guide assumes the root of your project already has a `Dockerfile` and a Kubernetes Deployment configuration file. For an example, see [google-github-actions](https://github.com/google-github-actions/setup-gcloud/tree/master/example-workflows/gke).

‎content/actions/deployment/deploying-to-your-cloud-provider/index.md‎

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
---
2+
title: Deploying to your cloud provider
3+
shortTitle: Deploying to your cloud provider
4+
intro: 'You can deploy to various cloud providers, such as AWS, Azure, and GKE.'
5+
versions:
6+
fpt: '*'
7+
ghae: 'issue-4856'
8+
ghec: '*'
9+
children:
10+
- /deploying-to-amazon-elastic-container-service
11+
- /deploying-to-azure-app-service
12+
- /deploying-to-google-kubernetes-engine
13+
---

‎content/actions/deployment/deploying-xcode-applications/index.md‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
---
2+
title: Deploying Xcode applications
3+
shortTitle: Deploying Xcode applications
4+
intro: 'You can sign Xcode apps within your continuous integration (CI) workflow by installing an Apple code signing certificate on {% data variables.product.prodname_actions %} runners.'
5+
versions:
6+
fpt: '*'
7+
ghae: 'issue-4856'
8+
ghec: '*'
9+
children:
10+
- /installing-an-apple-certificate-on-macos-runners-for-xcode-development
11+
---

content/actions/deployment/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md renamed to content/actions/deployment/deploying-xcode-applications/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,7 @@ title: Installing an Apple certificate on macOS runners for Xcode development
33
intro: 'You can sign Xcode apps within your continuous integration (CI) workflow by installing an Apple code signing certificate on {% data variables.product.prodname_actions %} runners.'
44
redirect_from:
55
- /actions/guides/installing-an-apple-certificate-on-macos-runners-for-xcode-development
6+
- /actions/deployment/installing-an-apple-certificate-on-macos-runners-for-xcode-development
67
versions:
78
fpt: '*'
89
ghes: '*'

0 commit comments

Comments
 (0)