mysql creation instruction does not specify resource group which means cleanup instructions won't remove mysql

[jeanfrancoislarente]

The instruction az mysql flexible-server create --public-access <YOUR-IP-ADDRESS> does not include the resource group, which means it creates a new resource group for the deployment. In the cleanup section of this tutorial, az group delete --name wordpress-project --yes --no-wait will only delete the AKS resources and not the mysql resources deployed.

I imagine the easy solution is to add the resource-group option to the az mysql flexible-server create instructions?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 70948431-95aa-5d2c-20f9-30796f4687bf
• Version Independent ID: 422d5d9a-e2a2-916c-52ba-892793b413a6
• Content: Tutorial: Deploy WordPress on AKS cluster with MySQL Flexible Server by using Azure CLI
• Content Source: articles/mysql/flexible-server/tutorial-deploy-wordpress-on-aks.md
• Service: mysql
• GitHub Login: @mksuni
• Microsoft Alias: sumuth

[AnuragSharma-MSFT]

@jeanfrancoislarente Thank you for the feedback. We are actively investigating and will get back to you soon.

[AnuragSharma-MSFT]

@jeanfrancoislarente Thanks for your patience. The commands which are mentioned run in local context of resource group that we created in the steps mentioned in the document. In this specific cases, we need not to provide the resource group at the time of creating the server, and then when we delete the resource group the resources including MySQL server will be deleted as well.

Please let us know if this helps.

[jeanfrancoislarente]

All other commands specify the resource group in them and I've never seen an az command run in context of a resource group before, so I'm not sure exactly what that means.

After the group creation in the instructions, you need to create a cluster, connect to it and eventually connect your cluster to the ACR, all in which you need to specify the resource group.

It would be easy, prudent and reasonable to add the --resource-group flag to the az mysql flexible-server create to the instructions. When I ran those instructions from my local computer's Windows Terminal, it created a completely new resource group - it did not create it in the same resource group.

It would also be nice to add --name to the the flexible-server mysql example and give it a nice example name, otherwise you're left with an automatically generated name serverxxxxxx. Finally I'd go so far to say it would be nice if you specified a --database-name. It's easy to do and would make it more intuitive to follow. "wordpress" as an example database name for a WordPress tutorial makes sense, as opposed to the default "flexibleserverdb".

Aside from the resource group thing, the other suggestions are far from critical but are feedback based on my experience of having freshly gone through the tutorial.

[AnuragSharma-MSFT]

@jeanfrancoislarente Thanks for responding back and I understand your concern. This is being assigned to the content author to evaluate and update as appropriate.

[markingmyname]

#reassign: @shreyaaithal

[markingmyname]

We sincerely apologize for the delayed response to this issue. I collaborate with the owners of the GitHub Issues related to PostgreSQL to help either get them resolved or determine how to update our documentation.

As such, is this GitHub Issue still a concern for you? If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion, and we will reopen the issue.

Due to the age of this issue, we will continue to close this issue.

Please visit https://docs.microsoft.com/en-us/answers/support/ for more information on asking questions about the product or service.

Thank you.

#please-close