azd env new validates the name/value being created

Allowed characters: Letters (a-z, A-Z), digits (0-9), hyphens (-), parentheses ((, )), underscores (_), and periods (.)
Maximum length: 64 characters
Special characters like #, $, %, *, / are NOT allowed

However, list simply does a ReadDir() and has no validation as you mention here if someone "manually" creates a folder/dir with invalid characters (not sure why they would do this motion) but ok.

Proposed Fix -

NAME          DEFAULT  LOCAL  REMOTE  STATUS
my-dev-env    true     true   false   ✓
#$#%*(#       false    true   false   ⚠ INVALID NAME
prod-env      false    true   true    ✓

add a summary warning -

⚠ Warning: 1 environment has an invalid name and may cause issues with azd commands.
  Use 'azd env help' to learn about valid environment names.

We could skip invalid names, but this hides problems/causes confusion and makes debugging hard. OR "FAIL HARD" - this is disruptive, doesn't help users fix this issue.

Additionally we need to protect other commands, env get, select etc should also validate so we cannot allow this invalid name.

Uh oh!

azd env list listing can contain invalid names #3355

Description

Activity

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

`azd env list` listing can contain invalid names #3355