Build and Review PR #8 #33
build-and-review-pr.yml
on: pull_request
build-and-review-pr
/
setup
8s
test-file-problems
9s
test-valid-files
5s
test-entities
4s
test-systems
5s
test-domains
3s
test-resources
4s
test-apis
3s
test-components
4s
build-and-review-pr
/
build-and-review-pr
13s
Annotations
61 errors and 60 warnings
Catalog Info Validation:
test/catalog-infos/invalid-domains.yml#L34
Doc 3, Line 34, Domain[cm-domain-3]/spec is an object that cannot be empty. It should contain both owner and type properties.
|
Catalog Info Validation:
test/catalog-infos/invalid-domains.yml#L45
Doc 4, Line 45, Domain[cm-domain-4]/spec must have required property owner.
|
Catalog Info Validation:
test/catalog-infos/invalid-domains.yml#L57
Doc 5, Line 57, Domain[cm-domain-5]/spec/owner is a string that cannot be empty. It should be populated or be removed completely if not required.
|
Catalog Info Validation:
test/catalog-infos/invalid-domains.yml#L69
Doc 6, Line 69, Domain[cm-domain-6]/spec/owner value content-management is invalid.
Expected Pattern: <kind>:[<optional-namespace>/]<entity-name> e.g. group:default/customization, group:customization, user:RyanHauert, user:default/RyanHauert
|
Catalog Info Validation:
test/catalog-infos/invalid-domains.yml#L81
Doc 7, Line 81, Domain[cm-domain-7]/spec must have required property type.
|
Catalog Info Validation:
test/catalog-infos/invalid-domains.yml#L95
Doc 8, Line 95, Domain[cm-domain-8]/spec/type value cannot be empty and must be one of the allowed values:
Core, External, Generic, Supporting
|
Catalog Info Validation:
test/catalog-infos/invalid-domains.yml#L108
Doc 9, Line 108, Domain[cm-domain-9]/spec/type value invalidThing is not one of the allowed values:
Core, External, Generic, Supporting
|
Catalog Info Validation:
test/catalog-infos/invalid-domains.yml#L111
Doc 10, Line 111, Domain[Doc10] must have required property metadata.
|
Catalog Info Validation:
test/catalog-infos/invalid-domains.yml#L124
Doc 11, Line 124, Domain[Doc11]/metadata is an object that cannot be empty. Metadata is required and should contain the required annotations property and an optional needs property.
|
Catalog Info Validation:
test/catalog-infos/invalid-domains.yml#L136
Doc 12, Line 136, Domain[cm-domain-12]/metadata/annotations is an object that cannot be empty. Annotations is a map of key-value pairs containing auxiliary information attached to the entity. For Domains, the mktp.io/notes annotation is required and any other annotations are optional.
|
Catalog Info Validation:
test/catalog-infos/invalid-apis.yml#L35
Doc 3, Line 35, API[content-mgmt-api-3]/spec is an object that cannot be empty. It should contain definition, lifecycle, system, and type properties and may contain an optional owner prop.
|
Catalog Info Validation:
test/catalog-infos/invalid-apis.yml#L44
Doc 4, Line 44, API[content-mgmt-api-4]/spec must have required property type.
|
Catalog Info Validation:
test/catalog-infos/invalid-apis.yml#L59
Doc 5, Line 59, API[content-mgmt-api-5]/spec/type value cannot be empty and must be one of the allowed values:
openapi, asyncapi
|
Catalog Info Validation:
test/catalog-infos/invalid-apis.yml#L73
Doc 6, Line 73, API[content-mgmt-api-6]/spec/type value myapi is not one of the allowed values:
openapi, asyncapi
|
Catalog Info Validation:
test/catalog-infos/invalid-apis.yml#L86
Doc 7, Line 86, API[content-mgmt-api-7]/spec must have required property lifecycle.
|
Catalog Info Validation:
test/catalog-infos/invalid-apis.yml#L102
Doc 8, Line 102, API[content-mgmt-api-8]/spec/lifecycle value cannot be empty and must be one of the allowed values:
experimenting, developing, maintaining, deprecating, obsolete
|
Catalog Info Validation:
test/catalog-infos/invalid-apis.yml#L116
Doc 9, Line 116, API[content-mgmt-api-9]/spec/lifecycle value mylifecycle is not one of the allowed values:
experimenting, developing, maintaining, deprecating, obsolete
|
Catalog Info Validation:
test/catalog-infos/invalid-apis.yml#L128
Doc 10, Line 128, API[content-mgmt-api-8]/spec must have required property system.
|
Catalog Info Validation:
test/catalog-infos/invalid-apis.yml#L145
Doc 11, Line 145, API[content-mgmt-api-11]/spec/system is a string that cannot be empty. It should be populated or be removed completely if not required.
|
Catalog Info Validation:
test/catalog-infos/invalid-apis.yml#L159
Doc 12, Line 159, API[content-mgmt-api-11]/spec/system value content-management is invalid.
Expected Pattern: system:[<optional-namespace>/]<system-name> e.g. system:default/appointment-manager, system:appointment-manager
|
Catalog Info Validation:
test/catalog-infos/invalid-entities.yml#L20
Doc 3, Line 20, System[content-management-3] must have required property apiVersion.
|
Catalog Info Validation:
test/catalog-infos/invalid-entities.yml#L28
Doc 4, Line 28, System[content-management-4]/apiVersion value cannot be empty and must be one of the allowed values:
backstage.io/v1alpha1, backstage.io/v1beta1
|
Catalog Info Validation:
test/catalog-infos/invalid-entities.yml#L35
Doc 5, Line 35, System[content-management-5]/apiVersion value invalid.version.io/v5 is not one of the allowed values:
backstage.io/v1alpha1, backstage.io/v1beta1
|
Catalog Info Validation:
test/catalog-infos/invalid-entities.yml#L43
Doc 6, Line 43, UnknownKind[content-management-6] must have required property kind.
|
Catalog Info Validation:
test/catalog-infos/invalid-entities.yml#L53
Doc 7, Line 53, UnknownKind[content-management-7]/kind value cannot be empty and must be one of the allowed values:
API, Component, Domain, Resource, System
|
Catalog Info Validation:
test/catalog-infos/invalid-entities.yml#L60
Doc 8, Line 60, Thing[content-management-8]/kind value Thing is not one of the allowed values:
API, Component, Domain, Resource, System
|
Catalog Info Validation:
test/catalog-infos/invalid-entities.yml#L67
Doc 9, Line 67, System[Doc9] must have required property metadata.
|
Catalog Info Validation:
test/catalog-infos/invalid-entities.yml#L78
Doc 10, Line 78, System[Doc10]/metadata is an object that cannot be empty. The metadata object requires a name property.
|
Catalog Info Validation:
test/catalog-infos/invalid-entities.yml#L85
Doc 11, Line 85, System[Doc11]/metadata/name is a string that cannot be empty. It should be populated or be removed completely if not required.
|
Catalog Info Validation:
test/catalog-infos/invalid-entities.yml#L94
Doc 12, Line 94, System[content-management-12]/metadata/title cannot be empty if provided.
|
Catalog Info Validation:
test/catalog-infos/invalid-components.yml#L44
Doc 3, Line 44, Component[content-mfe-3]/metadata/deployment-environments is an array that cannot be empty. It should contain at least one list item or be removed completely if not required.
|
Catalog Info Validation:
test/catalog-infos/invalid-components.yml#L57
Doc 4, Line 57, Component[content-mfe-4]/metadata/deployment-environments must NOT have duplicate items (items 2 and 0 are identical).
|
Catalog Info Validation:
test/catalog-infos/invalid-components.yml#L74
Doc 5, Line 74, Component[content-mfe-5]/spec is an object that cannot be empty. It should contain lifecycle, system, and type properties and may contain optional owner, subcomponentOf, providesApis, consumesApis and dependsOn props.
|
Catalog Info Validation:
test/catalog-infos/invalid-components.yml#L83
Doc 6, Line 83, Component[content-mfe-6]/spec must have required property type.
|
Catalog Info Validation:
test/catalog-infos/invalid-components.yml#L96
Doc 7, Line 96, Component[content-mfe-7]/spec/type value cannot be empty and must be one of the allowed values:
service, library, documentation, tool, mfe, site
|
Catalog Info Validation:
test/catalog-infos/invalid-components.yml#L108
Doc 8, Line 108, Component[content-mfe-8]/spec/type value InvalidResourceType is not one of the allowed values:
service, library, documentation, tool, mfe, site
|
Catalog Info Validation:
test/catalog-infos/invalid-components.yml#L119
Doc 9, Line 119, Component[content-mfe-9]/spec must have required property system.
|
Catalog Info Validation:
test/catalog-infos/invalid-components.yml#L133
Doc 10, Line 133, Component[content-mfe-10]/spec/system value cannot be empty.
Expected Pattern: system:[<optional-namespace>/]<system-name> e.g. system:default/appointment-manager, system:appointment-manager
|
Catalog Info Validation:
test/catalog-infos/invalid-components.yml#L145
Doc 11, Line 145, Component[content-mfe-11]/spec/system value content-management is invalid.
Expected Pattern: system:[<optional-namespace>/]<system-name> e.g. system:default/appointment-manager, system:appointment-manager
|
Catalog Info Validation:
test/catalog-infos/invalid-components.yml#L155
Doc 12, Line 155, Component[content-mfe-12]/spec must have required property lifecycle.
|
Catalog Info Validation:
test/catalog-infos/invalid-systems.yml#L24
Doc 3, Line 24, System[content-management-3]/spec is an object that cannot be empty. It should contain at least one optional domain or owner property or be removed completely.
|
Catalog Info Validation:
test/catalog-infos/invalid-systems.yml#L33
Doc 4, Line 33, System[content-management-4]/spec/owner is a string that cannot be empty. It should be populated or be removed completely if not required.
|
Catalog Info Validation:
test/catalog-infos/invalid-systems.yml#L42
Doc 5, Line 42, System[content-management-5]/spec/owner value content-management is invalid.
Expected Pattern: <kind>:[<optional-namespace>/]<entity-name> e.g. group:default/customization, group:customization, user:RyanHauert, user:default/RyanHauert
|
Catalog Info Validation:
test/catalog-infos/invalid-systems.yml#L51
Doc 6, Line 51, System[content-management-6]/spec/domain is a string that cannot be empty. It should be populated or be removed completely if not required.
|
Catalog Info Validation:
test/catalog-infos/invalid-systems.yml#L60
Doc 7, Line 60, System[content-management-7]/spec/domain value content-management-domain is invalid.
Expected Pattern: domain:[<optional-namespace>/]<domain-name> e.g. domain:default/front-end-tooling, domain:content-management
|
Catalog Info Validation:
test/catalog-infos/invalid-resources.yml#L33
Doc 3, Line 33, Resource[content-mgmt-db-3]/metadata/deployment-environments is an array that cannot be empty. It should contain at least one list item or be removed completely if not required.
|
Catalog Info Validation:
test/catalog-infos/invalid-resources.yml#L45
Doc 4, Line 45, Resource[content-mgmt-db-4]/metadata/deployment-environments must NOT have duplicate items (items 2 and 0 are identical).
|
Catalog Info Validation:
test/catalog-infos/invalid-resources.yml#L61
Doc 5, Line 61, Resource[content-mgmt-db-5]/spec is an object that cannot be empty. It should contain both system and type properties and may contain optional dependOn and owner props.
|
Catalog Info Validation:
test/catalog-infos/invalid-resources.yml#L70
Doc 6, Line 70, Resource[content-mgmt-db-6]/spec must have required property type.
|
Catalog Info Validation:
test/catalog-infos/invalid-resources.yml#L82
Doc 7, Line 82, Resource[content-mgmt-db-7]/spec/type value cannot be empty and must be one of the allowed values:
database, event-hub, app-gateway, front-door, fileshare, resource-group, external
|
Catalog Info Validation:
test/catalog-infos/invalid-resources.yml#L93
Doc 8, Line 93, Resource[content-mgmt-db-8]/spec/type value InvalidResourceType is not one of the allowed values:
database, event-hub, app-gateway, front-door, fileshare, resource-group, external
|
Catalog Info Validation:
test/catalog-infos/invalid-resources.yml#L103
Doc 9, Line 103, Resource[content-mgmt-db-9]/spec must have required property system.
|
Catalog Info Validation:
test/catalog-infos/invalid-resources.yml#L116
Doc 10, Line 116, Resource[content-mgmt-db-10]/spec/system value cannot be empty.
Expected Pattern: system:[<optional-namespace>/]<system-name> e.g. system:default/appointment-mananager, system:appointment-manager
|
Catalog Info Validation:
test/catalog-infos/invalid-resources.yml#L127
Doc 11, Line 127, Resource[content-mgmt-db-11]/spec/system value content-management is invalid.
Expected Pattern: system:[<optional-namespace>/]<system-name> e.g. system:default/appointment-mananager, system:appointment-manager
|
Catalog Info Validation:
test/catalog-infos/invalid-resources.yml#L139
Doc 12, Line 139, Resource[content-mgmt-db-12]/spec/owner is a string that cannot be empty. It should be populated or be removed completely if not required.
|
Catalog Info Validation:
test/catalog-infos/empty.yml#L1
./test/catalog-infos/empty.yml is empty.
|
Catalog Info Validation:
catalog-info.yml#L1
./catalog-info.yml does not exist.
|
test-file-problems
./catalog-info.yml file is invalid
|
Catalog Info Validation:
test/catalog-infos/comments-only.yml#L1
./test/catalog-infos/comments-only.yml only contains comments.
|
Catalog Info Validation:
catalog-info.yml#L1
./catalog-info.yml does not exist.
|
build-and-review-pr / build-and-review-pr
Before this PR can be merged, the following item(s) should be addressed to comply with the action's Contributing Guidelines.
- Please ensure the action has been recompiled by running the following command from the root of the repository:
`npm run build`
|
test-domains
Doc #3 is invalid
|
test-domains
Doc #4 is invalid
|
test-domains
Doc #5 is invalid
|
test-domains
Doc #6 is invalid
|
test-domains
Doc #7 is invalid
|
test-domains
Doc #8 is invalid
|
test-domains
Doc #9 is invalid
|
test-domains
Doc #10 is invalid
|
test-domains
Doc #11 is invalid
|
test-domains
Doc #12 is invalid
|
test-apis
Doc #3 is invalid
|
test-apis
Doc #4 is invalid
|
test-apis
Doc #5 is invalid
|
test-apis
Doc #6 is invalid
|
test-apis
Doc #7 is invalid
|
test-apis
Doc #8 is invalid
|
test-apis
Doc #9 is invalid
|
test-apis
Doc #10 is invalid
|
test-apis
Doc #11 is invalid
|
test-apis
Doc #12 is invalid
|
test-entities
Doc #3 is invalid
|
test-entities
Doc #4 is invalid
|
test-entities
Doc #5 is invalid
|
test-entities
Doc #6 is invalid
|
test-entities
Doc #7 is invalid
|
test-entities
Doc #8 is invalid
|
test-entities
Doc #9 is invalid
|
test-entities
Doc #10 is invalid
|
test-entities
Doc #11 is invalid
|
test-entities
Doc #12 is invalid
|
test-components
Doc #3 is invalid
|
test-components
Doc #4 is invalid
|
test-components
Doc #5 is invalid
|
test-components
Doc #6 is invalid
|
test-components
Doc #7 is invalid
|
test-components
Doc #8 is invalid
|
test-components
Doc #9 is invalid
|
test-components
Doc #10 is invalid
|
test-components
Doc #11 is invalid
|
test-components
Doc #12 is invalid
|
test-systems
Doc #3 is invalid
|
test-systems
Doc #4 is invalid
|
test-systems
Doc #5 is invalid
|
test-systems
Doc #6 is invalid
|
test-systems
Doc #7 is invalid
|
test-systems
./test/catalog-infos/invalid-systems.yml file is invalid
|
test-resources
Doc #3 is invalid
|
test-resources
Doc #4 is invalid
|
test-resources
Doc #5 is invalid
|
test-resources
Doc #6 is invalid
|
test-resources
Doc #7 is invalid
|
test-resources
Doc #8 is invalid
|
test-resources
Doc #9 is invalid
|
test-resources
Doc #10 is invalid
|
test-resources
Doc #11 is invalid
|
test-resources
Doc #12 is invalid
|
build-and-review-pr / setup
The following actions use a deprecated Node.js version and will be forced to run on node20: im-open/git-version-lite@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-file-problems
./test/catalog-infos/empty.yml file is invalid
|
test-file-problems
./test/catalog-infos/comments-only.yml file is invalid
|
test-file-problems
./catalog-info.yml file is invalid
|