Resource Instance Name constraints

[ThomasNieto]

Prerequisites

• Write a descriptive title.
• Make sure you are able to repro it on the latest version
• Search the existing issues.

Summary

I would like to use periods . in my resource instance name but the schema says that is not allowed. Is there a technical reason for only allowing spaces, letters and numbers?

See below #845 (comment) for the issues it causes with dsc config/resource export because the auto created document uses resource type name which contains periods, forward slashes, hyphens, and underscore.

https://raw.githubusercontent.com/PowerShell/DSC/main/schemas/v3/definitions/instanceName.json

The short, human-readable name for a DSC resource instance. Must be unique within a DSC Configuration document. Must be a non-empty string containing only letters, numbers, and spaces

Steps to reproduce

n/a

Expected behavior

n/a

Actual behavior

n/a

Error details

Environment data

n/a

Version

3.1-preview6

Visuals

No response

[ThomasNieto]

This also causes issues with dsc config/resource export as the name of the resource instance is resource type followed by a hyphen and counter.