Skip to content

Naming restrictions #2112

Open
Open

Description

Currently, we don't have schema or logic that enforces naming restrictions for important names in azure.yaml or environment name.

This can lead to unexpected errors, because we use some of these names to construct derived names that are subjected to naming validations from other tools and services.

The current known list:

Project Name (name in azure.yaml)

  1. Docker. Used for default naming of a Docker image name.

Service Name (service.name in azure.yaml)

  1. Docker. Used for default naming of a Docker image name.

Environment Name

  1. Azure. Used for generation of a deployment name.
  2. Azure. Used for generation of tags.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions