-
Task
-
Resolution: Done
-
Normal
-
None
-
None
-
None
-
Product / Portfolio Work
-
False
-
-
False
-
None
-
Unset
-
None
-
-
Proposed design for storing and validating JSON schemas/payloads
- The validation will take the respective schemas and validate resources/reporters based on the file names/directories in this setup
- In this example k8s_cluster.json defines the required fields of a resource_type
- Reporterdata will then be validated seperatly after the resource data
└── resources
│ ├── k8s_cluster
│ │ ├── config.yaml # Defines what reporters can be associated with a resource│ │ ├── k8s_cluster.json # resource type schema│ │ └── reporters
│ │ ├── acm
│ │ │ ├── acm.json # reporter type JSON schema│ │ │ ├── config.yaml # define relation properties/namespace│ │ │
│ │ └── ocm
│ │ ├── config.yaml # define relation properties/namespace│ │ └── ocm.json # reporter type JSON schema
Acceptance criteria
- Finalize the Schema structure for the Resource configurations
- is depended on by
-
RHCLOUD-37565 Make E2E tests self serviceable
-
- Refinement
-