-
Notifications
You must be signed in to change notification settings - Fork 255
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
16 changed files
with
189 additions
and
31 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,76 @@ | ||
--- | ||
title: Update to a new release | ||
geekdocCollapseSection: true | ||
weight: 71 | ||
--- | ||
|
||
## What is the latest release | ||
|
||
The list of enhancement, additions and fixed bugs contained in every release can be seen by navigating to corresponding page linked in the home page of the [azure-monitor-baseline-alerts](https://github.com/Azure/azure-monitor-baseline-alerts) repository. | ||
|
||
On the center-right side of the page there's a specific section indicating the latest release. Click on the release number to see the release content. | ||
|
||
![Releases](../media/Releases.png) | ||
|
||
</br> | ||
|
||
## Steps to update to the latest release | ||
|
||
This section will guide you through the necessary steps to update the current deployment with the latest enhancements contained in the latest release. Guidance on updating to releases containing breaking changes is not in scope and could eventually be described in a dedicated pages. | ||
|
||
{{< hint type=Important >}} | ||
This scenario only applies to AMBA deployments performed using GitHub. If not using GitHub, please refer to the [Can I use AMBA without a GitHub repository](../FAQ/#can-i-use-amba-without-a-github-repository) scenario documented in the *Frequently Asked Questions* making sure you update the template spec as required. | ||
{{< /hint >}} | ||
|
||
Depending if you used the official code from the official GitHub repository or from a forked one, not all the high-level steps below are required: | ||
|
||
1. Sync your fork *(only required if you forked the original repo)* | ||
2. Update your local copy of the repo *(only required if you cloned your fork on your local hard drive)* | ||
3. Deploy ***(always required)*** | ||
|
||
### Sync your fork (only required if you forked the original repo) | ||
|
||
Synching a fork means that we're making sure any update made to the main branch in the official repo is replicated over yours. To sync your fork: | ||
|
||
1. Open the your GitHub repo page. If you don't remember the URL, consider that it normally looks like `https://github.com/***<YourGitHubId>***/azure-monitor-baseline-alerts`. | ||
2. You should be redirected to the default page which is **<> Code**. If not, click on the **<> Code** tab. | ||
|
||
![<> Code](../media/GitHub_Code.png) | ||
|
||
3. Click on the **Sync fork** and then select **Update branch** | ||
|
||
![Update branch](../media/UpdateBranch.png) | ||
|
||
4. Refresh the page and make sure to see the description reported in the picture below on the left of the **Contribute** and **Sync fork** buttons | ||
|
||
![Branch is up to date](../media/BranchUpToDate.png) | ||
|
||
</br> | ||
|
||
### Update your local copy (only required if you cloned your fork on your local hard drive) | ||
|
||
Within the code editor of your choice, make sure you pull the changes from your remote fork. Pulling changes from origin/main is necessary to ensure that the local branch is exactly the same as the remote. In this guide, we will use VSCode. | ||
|
||
1. Open VSCode and open the folder containing the cloned repo. | ||
2. In the bottom-left corner click on the pull icon | ||
|
||
![Pull icon](../media/PullIcon.png) | ||
|
||
3. Confirm or approve the operation if necessary | ||
|
||
![Confirm pull](../media/ConfirmPull.png) | ||
|
||
4. Ensure there are no issues with pulling changes and that the numbers close to the icon in the bottom-left corner are both **0** or not showing at all | ||
|
||
![Pull request completed](../media/PullCompleted.png) | ||
|
||
</br> | ||
|
||
### Deploy (always required) | ||
|
||
Once you reached this stage, you are ready to deploy the latest release. You can deploy using a method of your choice among the allowed one: | ||
|
||
- To deploy with GitHub Actions, please proceed with [Deploy with GitHub Actions](../deploy/Deploy-with-GitHub-Actions) | ||
- To deploy with Azure DevOps Pipelines, please proceed with [Deploy with Azure Pipelines](../deploy/Deploy-with-Azure-Pipelines) | ||
- To deploy with Azure CLI, please proceed with [Deploy with Azure CLI](../deploy/Deploy-with-Azure-CLI) | ||
- To deploy with Azure PowerShell, please proceed with [Deploy with Azure PowerShell](../deploy/Deploy-with-Azure-PowerShell) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,4 @@ | ||
--- | ||
title: ApiManagement | ||
geekdocCollapseSection: true | ||
geekdocHidden: true | ||
--- |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,7 +1,6 @@ | ||
--- | ||
title: service | ||
geekdocCollapseSection: true | ||
geekdocHidden: true | ||
--- | ||
|
||
{{< alertList name="alertList" >}} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters