Slash '/' in 'name:' of azure.yaml will break service packaging

[crpietschmann]

• 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.11.0 (commit 5b92e0687e1fa96dfc8292f4b900c0c58610b6a5)

Describe the bug
When the name: within azure.yaml contains a slash / character, it breaks the packaging of services.

error that ocurrs:

root@MacBookPro azd-react-bootstrap-dashboard # azd package api

Packaging services (azd package)

  (x) Failed: Packaging service api

ERROR: failed packaging service 'api': failed when creating zip package to deploy api: open /tmp/build5nines/azd-react-bootstrap-dashboard-api-azddeploy-1734478898.zip: no such file or directory

To Reproduce

1. change the name: of the template in the azure.yaml file to have a slash / character in it; such as `build5nines/azd-react-bootstrap-dashboard'
2. add a service for a web project, such as a node.js app

Expected behavior
It's expected that the service packaging complete successfully, or gives a warning that the name contains an invalid character.

root@MacBookPro azd-react-bootstrap-dashboard # azd package api     

Packaging services (azd package)

  (✓) Done: Packaging service api
  - Package Output: /tmp/build5nines-azd-react-bootstrap-dashboard-api-azddeploy-1734479080.zip

  (-) Skipped: Packaging service dashboard

Environment
Information on your environment:
* Language name and version: Node.js v23.3.0
* IDE and version : Latest VS Code
* OS: macOS

Additional context
Add any other context about the problem here.

[NanaXiong00]

This issue can be reproduced, and we will fix it in the following approach:

If there is a slash / in the "name:" of azure.yaml, change the / to - when packaging without any prompts.

CC: @rajeshkamal5050

[Menghua1]

This issue can be reproduced, and we will fix it in the following approach:

If there is a slash / in the "name:" of azure.yaml, change the / to - when packaging without any prompts.

@vhvb1989 What do you think about this approach? Should we silently replace / with -, or would it be better to warn the user that the name contains an invalid character and prompt them to fix it?

[vhvb1989]

Thanks for taking thins @Menghua1

I'm worried about bringing some other issues by doing a silent-replace. I'd prefer to update the azure.yaml schema to set naming rules for the field name so it gets highlighted when folks adds something invalid like a / or some other symbol.

We can also make AZD to start by checking the name and failing if finding something invalid.

[Menghua1]

Hi @vhvb1989, I’ve opened a PR #5380 to fix this issue. Could you please review it? Thank you!