Skip to content

[Entities]: Add Entity Validity State. Part#2 #465

@siarhei-fedziukovich

Description

@siarhei-fedziukovich

Name and Version

0.12.0

What is the problem this feature will solve?

the same as #122

What is the feature you are proposing to solve the problem?

the same as #122

new validity rules:

Validation Rules:

ApplicationTypeSchema
Applications
  • applicationTypeSchema - invalid if parentApplicationTypeSchema is invalid
Toolsets
  • containerSource - invalid if deployment not defined or does not exists in DM
Models
  • containerSource - invalid if deployment not defined or does not exists in DM
Interceptor
  • interceptor_configuration - invalid if incompatible with schema provided in configurationEndpoint (not sure here. because it will still valid in config for core and fail during execution)
  • containerSource - invalid if deployment not defined or does not exists

What alternatives have you considered?

No response

Metadata

Metadata

Type

No type

Projects

Status

To-Do

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions