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
Copy file name to clipboardExpand all lines: README.md
+26-26Lines changed: 26 additions & 26 deletions
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,10 @@
1
-
# NGINX for Azure Deployment Action
1
+
# NGINXaaS for Azure Deployment Action
2
2
3
-
This action supports managing the configuration of an [NGINX for Azure](https://docs.nginx.com/nginx-for-azure/quickstart/overview/) deployment in a GitHub repository. It enables continuous deployment through GitHub workflows to automatically update the NGINX for Azure deployment when changes are made to the NGINX configuration files stored in the respository. Additionally, one can update NGINX certificates that are already present in Azure key vault.
3
+
This action supports managing the configuration of an [NGINXaaS for Azure](https://docs.nginx.com/nginxaas/azure/quickstart/overview/) deployment in a GitHub repository. It enables continuous deployment through GitHub workflows to automatically update the NGINXaaS for Azure deployment when changes are made to the NGINX configuration files stored in the repository. Additionally, one can update NGINX certificates that are already present in Azure key vault.
4
4
5
5
## Connecting to Azure
6
6
7
-
This action leverages the [Azure Login](https://github.com/marketplace/actions/azure-login) action for authenticating with Azure and performing update to an NGINX for Azure deployment. Two different ways of authentication are supported:
7
+
This action leverages the [Azure Login](https://github.com/marketplace/actions/azure-login) action for authenticating with Azure and performing update to an NGINXaaS for Azure deployment. Two different ways of authentication are supported:
8
8
-[Service principal with secrets](https://docs.microsoft.com/en-us/azure/developer/github/connect-from-azure?tabs=azure-portal%2Cwindows#use-the-azure-login-action-with-a-service-principal-secret)
9
9
-[OpenID Connect](https://docs.microsoft.com/en-us/azure/developer/github/connect-from-azure?tabs=azure-portal%2Cwindows#use-the-azure-login-action-with-openid-connect) (OIDC) with an Azure service principal using a Federated Identity Credential
10
10
@@ -13,7 +13,7 @@ This action leverages the [Azure Login](https://github.com/marketplace/actions/a
13
13
```yaml
14
14
# File: .github/workflows/nginxForAzureDeploy.yml
15
15
16
-
name: Sync the NGINX configuration from the GitHub repository to an NGINX for Azure deployment
16
+
name: Sync the NGINX configuration from the GitHub repository to an NGINXaaS for Azure deployment
17
17
on:
18
18
push:
19
19
branches:
@@ -33,7 +33,7 @@ jobs:
33
33
with:
34
34
creds: ${{ secrets.AZURE_CREDENTIALS }}
35
35
36
-
- name: 'Sync the NGINX configuration from the GitHub repository to the NGINX for Azure deployment'
36
+
- name: 'Sync the NGINX configuration from the GitHub repository to the NGINXaaS for Azure deployment'
To facilitate the migration of the existing NGINX configuration, NGINX for Azure supports multiple-files configuration with each file uniquely identified by a file path, just like how NGINX configuration files are created and used in a self-hosting machine. An NGINX configuration file can include another file using the [include directive](https://docs.nginx.com/nginx/admin-guide/basic-functionality/managing-configuration-files/). The file path used in an `include` directive can either be an absolute path or a relative path to the [prefix path](https://www.nginx.com/resources/wiki/start/topics/tutorials/installoptions/).
91
+
To facilitate the migration of the existing NGINX configuration, NGINXaaS for Azure supports multiple-files configuration with each file uniquely identified by a file path, just like how NGINX configuration files are created and used in a self-hosting machine. An NGINX configuration file can include another file using the [include directive](https://docs.nginx.com/nginx/admin-guide/basic-functionality/managing-configuration-files/). The file path used in an `include` directive can either be an absolute path or a relative path to the [prefix path](https://www.nginx.com/resources/wiki/start/topics/tutorials/installoptions/).
92
92
93
-
The following example shows two NGINX configuration files inside the `/etc/nginx` directory on disk are copied and stored in a GitHub respository under its `config` directory.
93
+
The following example shows two NGINX configuration files inside the `/etc/nginx` directory on disk are copied and stored in a GitHub repository under its `config` directory.
94
94
95
-
| File path on disk | File path in the respository |
To use this action to sync the configuration files from this example, the directory path relative to the GitHub repository root `config/` is set to the action's input `nginx-config-directory-path` for the action to find and package the configuration files. The root file `nginx.conf` is set to the input `nginx-root-config-file`.
101
101
102
102
```yaml
103
-
- name: 'Sync the NGINX configuration from the GitHub repository to the NGINX for Azure deployment'
103
+
- name: 'Sync the NGINX configuration from the GitHub repository to the NGINXaaS for Azure deployment'
@@ -110,12 +110,12 @@ To use this action to sync the configuration files from this example, the direct
110
110
nginx-root-config-file: nginx.conf
111
111
```
112
112
113
-
By default, the action uses a file's relative path to `nginx-config-directory-path` in the respository as the file path in the NGINX for Azure deployment.
113
+
By default, the action uses a file's relative path to `nginx-config-directory-path` in the repository as the file path in the NGINXaaS for Azure deployment.
114
114
115
-
| File path on disk | File path in the respository | File path in the NGINX for Azure deployment |
The default file path handling works for the case of using relative paths in `include` directives, for example, if the root `nginx.conf` references `mysite.conf` using:
121
121
@@ -129,10 +129,10 @@ For the case of using absolute paths in `include` directives, for example, if th
129
129
include /etc/nginx/sites-enabled/mysite.conf;
130
130
```
131
131
132
-
The action supports an optional input `transformed-nginx-config-directory-path` to transform the absolute path of the configuration directory in the NGINX for Azure deployment. The absolute configuration directory path on disk `/etc/nginx/` can be set to `transformed-nginx-config-directory-path` as follows to ensure the configuration files using absolute paths in `include` directives work as expected in the NGINX for Azure deployment.
132
+
The action supports an optional input `transformed-nginx-config-directory-path` to transform the absolute path of the configuration directory in the NGINXaaS for Azure deployment. The absolute configuration directory path on disk `/etc/nginx/` can be set to `transformed-nginx-config-directory-path` as follows to ensure the configuration files using absolute paths in `include` directives work as expected in the NGINXaaS for Azure deployment.
133
133
134
134
```yaml
135
-
- name: 'Sync the NGINX configuration from the Git repository to the NGINX for Azure deployment'
135
+
- name: 'Sync the NGINX configuration from the Git repository to the NGINXaaS for Azure deployment'
description: "The action synchronizes NGINX configuration from a Git repository and/or certificates already on Azure keyvault to an NGINX for Azure deployment"
1
+
name: "NGINXaaS for Azure Deployment Sync"
2
+
description: "The action synchronizes NGINX configuration from a Git repository and/or certificates already on Azure keyvault to an NGINXaaS for Azure deployment"
3
3
inputs:
4
4
subscription-id:
5
-
description: "The Azure subscription ID of the NGINX for Azure deployment."
5
+
description: "The Azure subscription ID of the NGINXaaS for Azure deployment."
6
6
required: true
7
7
resource-group-name:
8
-
description: "The resource group of the NGINX for Azure deployment."
8
+
description: "The resource group of the NGINXaaS for Azure deployment."
9
9
required: true
10
10
nginx-deployment-name:
11
-
description: "The name of the NGINX for Azure deployment."
11
+
description: "The name of the NGINXaaS for Azure deployment."
12
12
required: true
13
13
nginx-deployment-location:
14
14
description: "The location where the NGINX deployment is located. Example westcentralus"
@@ -23,9 +23,9 @@ inputs:
23
23
default: "nginx.conf"
24
24
transformed-nginx-config-directory-path:
25
25
description: >
26
-
'The transformed absolute path of the NGINX configuration directory in NGINX for Azure deployment, example: "/etc/nginx/".
26
+
'The transformed absolute path of the NGINX configuration directory in NGINXaaS for Azure deployment, example: "/etc/nginx/".
27
27
If the "include" directive in the NGINX configuration files uses absolute paths, the path transformation
28
-
can be used to overwrite the file paths when the action synchronizes the files to the NGINX for Azure deployment.'
28
+
can be used to overwrite the file paths when the action synchronizes the files to the NGINXaaS for Azure deployment.'
29
29
required: false
30
30
default: ""
31
31
nginx-certificates:
@@ -34,11 +34,11 @@ inputs:
34
34
runs:
35
35
using: "composite"
36
36
steps:
37
-
- name: "Synchronize NGINX certificate(s) from the Git repository to an NGINX for Azure deployment"
37
+
- name: "Synchronize NGINX certificate(s) from the Git repository to an NGINXaaS for Azure deployment"
0 commit comments