30 character limit for Blueprint identifier/title is too restrictive
S
Stevan Vanderwerf
For some use cases the 30 character limit is restrictive and limits the capacity for some advanced workflows for auto-generating blueprints from a service prepended with some prefixes. An increase in the character limit would enable advanced use cases/workflows without having to resort to brittle workarounds.
Dudi - Port team
Merged in a post:
Increase Character Limit for Property identifier and title
Priya Raghu
Currently when creating a new property, there is a 30 character limit for identifier and title. Increase in the limit would be helpful.
M
Mark Tarry
Agreed.
We have adopted a convention for all metric properties, to use
metric_<type>_<name>
- e.g. metric_count_total_deployments
That example is bang on 30 characters, but it's very easy to go over the limit when applying such conventions.
M
Mark Tarry
Agreed. The same applies to blueprint property names.
We have adopted a convention for all metric properties, to use
metric_<type>_<name>
- e.g. metric_count_total_deployments
That example is bang on 30 characters, but it's very easy to go over the limit when applying such conventions.
S
Simon Beaulieu
Other request mentioning the same: