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
The service principal being used for authenticating with Azure should have access to manage the NGINXaaS deployment. For simplicity, this guide assumes that the service principal has `Contributor` role to manage the deployment. Refer [prerequisites](https://docs.nginx.com/nginxaas/azure/getting-started/prerequisites/) for details.
91
+
89
92
## Handling NGINX configuration file paths
90
93
91
94
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/).
@@ -101,7 +104,7 @@ To use this action to sync the configuration files from this example, the direct
101
104
102
105
```yaml
103
106
- name: 'Sync the NGINX configuration from the GitHub repository to the NGINXaaS for Azure deployment'
@@ -151,11 +154,11 @@ The transformed paths of the two configuration files in the NGINXaaS for Azure d
151
154
152
155
## Handling NGINX certificates
153
156
154
-
Since certificates are secrets, it is assumed they are stored in Azure key vault. One can provide multiple certificate entries to the github action as an array of JSON objects with keys:
157
+
Since certificates are secrets, it is assumed they are stored in Azure key vault. One can provide multiple certificate entries to the github action as an array of JSON objects with keys:
155
158
156
159
`certificateName`- A unique name for the certificate entry
157
160
158
-
`keyvaultSecret`- The secret ID for the certificate on Azure key vault
161
+
`keyvaultSecret`- The secret ID for the certificate on Azure key vault
159
162
160
163
`certificateVirtualPath`- This path must match one or more ssl_certificate directive file arguments in your Nginx configuration; and must be unique between certificates within the same deployment
161
164
@@ -165,7 +168,7 @@ See the example below
165
168
166
169
```yaml
167
170
- name: "Sync NGINX certificates to NGINXaaS for Azure"
0 commit comments