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
### Input repository information directly to the Azure portal
131
132
132
-
###Import `application.yml` file from your local machine
133
+
#### Default repository
133
134
134
-
You can import your `application.yml` file directly from your local machine to Azure Spring Cloud. Click the **Import settings**button, then select the `.yml` file from your project directory. Click **Import**, then an `async` operation from your **Notifications**will pop up. After 1-2 minutes, it should report sucesss.
135
+
* Public repository: In the **Default repository**section, paste the repository URI in the **Uri** section and ensure the **Authentication**setting is **Public**. Then click **Apply** to finish.
* Private repository: Azure Spring Cloud supports basic password/token based authentication and SSH.
137
138
138
-
### Public repository
139
+
* Basic Authentication: In the **Default repository** section, paste the repository's URI in the **Uri** section, then click the **Authentication**. Select **Basic** as your **Authentication type** and enter your username and password/token to grant access to Azure Spring Cloud. Click **OK** and **Apply** to finish setting up your Config Server.
139
140
140
-
If your repository is public: In the **Default repository** section, paste the repository URI in the **Uri** section and ensure the **Authentication** setting is **Public**. Then click **Apply** to finish.
> Some Git repository servers like GitHub use a `personal-token` or a `access-token` like a password for **Basic Authentication**. You can use that kind of token as password in Azure Spring Cloud, as it will never expire. But for other Git repository servers such as BitBucket and Azure DevOps, the `access-token` will expire in one or two hours. This means that option not viable when using those repository servers with Azure Spring Cloud.]
141
145
142
-
### Private repository
146
+
* SSH: In the **Default repository** section, paste the repository's URI in the **Uri** section, then click the **Authentication**. Select **SSH** as your **Authentication type** and enter your **Private key**. You can optionally specify your **Host key** and **Host key algorithm**. Be sure to include your public key in your config server repository. Click **OK** and **Apply** to finish setting up your Config Server.
143
147
144
-
Azure Spring Cloud supports basic password/token based authentication and SSH.
In the **Default repository**section, paste the repository's URI in the **Uri**section, then click the **Authentication**. Select **Basic**as your**Authentication type** and enter your username and password/token to grant access to Azure Spring Cloud. Click **OK**and **Apply** to finish setting up your Config Server.
152
+
If you want to use an optional **Pattern repository**to configure your service, specify the **URI**and **Authentication** the same way as the**Default repository**. Be sure to include a **Name**for your pattern, then click **Apply** to attach it to your instance.
> Some Git repository servers like GitHub use a `personal-token` or a `access-token` like a password for **Basic Authentication**. You can use that kind of token as password in Azure Spring Cloud, as it will never expire. But for other Git repository servers such as BitBucket and Azure DevOps, the `access-token` will expire in one or two hours. This means that option not viable when using those repository servers with Azure Spring Cloud.
156
+
If you have written a YAML file with your repository settings, you can import your YAML file directly from your local machine to Azure Spring Cloud. A simple YAML file for a private repository with basic authentication would look like this:
Click the **Import settings** button, then select the `.yml` file from your project directory. Click **Import**, then an `async` operation from your **Notifications** will pop up. After 1-2 minutes, it should report success.
In the **Default repository** section, paste the repository's URI in the **Uri** section, then click the **Authentication**. Select **SSH** as your **Authentication type** and enter your **Private key**. You can optionally specify your **Host key** and **Host key algorithm**. Be sure to include your public key in your config server repository. Click **OK** and **Apply** to finish setting up your Config Server.
175
+
You should see the information from your YAML file displayed in the Azure portal. Click **Apply** to finish.
0 commit comments