From b2b3def7041bb4f3178c3ae49ba62f36af663471 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fredrik=20Adel=C3=B6w?= Date: Tue, 19 May 2020 15:03:19 +0200 Subject: [PATCH] Lied about the name format --- .../adr002-default-catalog-file-format.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/docs/architecture-decisions/adr002-default-catalog-file-format.md b/docs/architecture-decisions/adr002-default-catalog-file-format.md index d8d5ff4025..23db32cc9c 100644 --- a/docs/architecture-decisions/adr002-default-catalog-file-format.md +++ b/docs/architecture-decisions/adr002-default-catalog-file-format.md @@ -130,10 +130,8 @@ Names are required to follow a certain format. Entities that do not follow those will not be accepted for registration in the catalog. The ruleset is configurable to fit your organization's needs, but the default behavior is as follows. -- Strings of length at least 1, and at most 253 -- Consist only of URL safe characters, e.g. ones that `encodeURIComponent` or similar would - leave unchanged -- Must consist of sequences of `[a-z0-9A-Z]` possibly separated by other characters +- Strings of length at least 1, and at most 63 +- Must consist of sequences of `[a-z0-9A-Z]` possibly separated by one of `[-_.]` Example: `visits-tracking-service`, `CircleciBuildsDs_avro_gcs`