Schema for Jarvisv2 Predefined Profiles

From PredefinedProfiles.schema.yaml (jarvisv2/PredefinedProfiles.schema)

---
$defs:
  HospitalProfileMetadata:
    description: Profile metadata associated with a hospital user.
    properties:
      institution:
        anyOf:
        - type: string
        - type: 'null'
        default: null
        description: The institution that the user belongs to. This is usually similar
          to the tenant
        title: Institution
    title: HospitalProfileMetadata
    type: object
  JarvisProfile:
    description: Profile for Jarvis V2.
    properties:
      hospital:
        anyOf:
        - $ref: '#/$defs/HospitalProfileMetadata'
        - type: 'null'
        default: null
        description: Profile metadata associated with a hospital user.
        title: Hospital
      tenant:
        anyOf:
        - description: The `cleo` app tenant applicable to this object.
          pattern: ^cleo\:[a-zA-Z0-9][\w\-\_]*$
          title: Cleo Tenant
          type: string
        - description: The `hospital` app tenant applicable to this object.
          pattern: ^hospital\:[a-zA-Z0-9][\w\-\_]*$
          title: Hospital Tenant
          type: string
        description: The tenant of this profile.
        title: Tenant
    required: [tenant]
    title: JarvisProfile
    type: object
$id: https://skeleton.botmd.io/jarvisv2/PredefinedProfiles.schema
$schema: http://json-schema.org/draft-07/schema#
description: Predefined profiles for Jarvis. This can be used in Jarvis test framework
  as well as in the Jarvis CLI.
properties:
  profiles:
    additionalProperties:
      $ref: '#/$defs/JarvisProfile'
    description: The predefined profiles.
    title: Profiles
    type: object
title: Predefined Profiles
type: object

[Main Page] [Schema Documentation] [Examples]