1
0
Форкнуть 0
This commit is contained in:
Yev Bronshteyn 2020-02-01 17:16:43 -08:00
Родитель fd669cbb48
Коммит 327afbcc3b
2 изменённых файлов: 25 добавлений и 0 удалений

Просмотреть файл

@ -139,3 +139,5 @@ __Note:__ the prior deployment does not automatically get deleted. It's still av
--- ---
⬅️ Previous section: [04 - Enable Continuous Deployment](../04-enable-continuous-deployment/README.md) ⬅️ Previous section: [04 - Enable Continuous Deployment](../04-enable-continuous-deployment/README.md)
➡️ Next section: [Conclusion](../99-conclusion/README.md)

23
99-conclusion/README.md Normal file
Просмотреть файл

@ -0,0 +1,23 @@
# Conclusion
## Cleaning up
Unless you plan to perform additional tasks with the Azure resources from the workshop (such as tutorials referenced below), it is important to destroy the resources that we created for it to avoid the cost of keeping them provisioned.
The easiest way to do this is to delete the entire resource group.
>🛑Substitute the name of your resource group for `$RESOURCE_GROUP_NAME` below:
```bash
az group delete -g "$RESOURCE_GROUP_NAME" --yes --no-wait
```
## Additional Resources
As an addendum to this workshop, consider taking the [tutorial on using alerts and action groups with Azure Spring Cloud](https://docs.microsoft.com/azure/spring-cloud/spring-cloud-tutorial-alerts-action-groups/?WT.mc_id=azurespringcloud-github-judubois) to detect and respond to aberrant conditions.
Have a look through the [Azure Spring Cloud documentation](https://docs.microsoft.com/azure/spring-cloud/?WT.mc_id=azurespringcloud-github-judubois) for more quickstarts, tutorials, and reference materials.
---
⬅️ Previous section: [05 - Enable Blue-Green Deployment](../05-enable-blue-green-deployment/README.md)