• Make sure you've installed the latest version using instructions in the wiki

Output from azd version
Run azd version and copy and paste the output here:
azd version 1.7.0 (commit 49d6adc2efb178083f61822e6b4715258560803d)

Describe the bug
In one of the initial iterations of an example I was using, I left the name value in the azure.yaml file to be ode-... This resulted in a namespace being created in the cluster with todo-nodejs... But this didn't look right for the demo, so I changed the name to taurus-dev. (In the final demo, this was reverb-dev.)
When I did this, a new namespace was created in the cluster BUT, azd deploy did not deploy the built containers to the new namespace. Everything always went to the first namespace created, in this case todo-node...

To Reproduce
in dev center mode
using one of the todo samples with aks...

• azd init
• azd provision
• azd deploy

Then edit the azure.yaml file

• azd deploy

Expected behavior
the latest container from the container registry should be deployed into the new namespace, but it is not. it's deployed into the original namespace.

Environment
Information on your environment:
* running in dev center mode
* CLI

Additional context