Application definition

interface Metadata {
    description?: string;
    instanceId: string;
    links?: { about?: string; related?: string; self?: string };
    name: string;
    namespace?: `x-${string}`;
    release: string;
    serviceGroupId?: string;
    serviceId?: string;
    tags?: string[];
    version: string;
}

Hierarchy (View Summary)

Properties

description?: string

Service description

`My own service description`
instanceId: string

Service instance unique identification within the scope of the service identification

`085f47e9-7fad-4da1-b5e5-31fc6eed9f94`
links?: { about?: string; related?: string; self?: string }

Service related links

Type declaration

  • Optionalabout?: string

    About link for the service

    `https://www.mytra.es/about`
    
  • Optionalrelated?: string

    Related link for the service

    `https://www.mytra.es`
    
  • Optionalself?: string

    Link to the own service or health endpoint

    `http://localhost:3000/v1/health`
    
name: string

Service name

`myOwnService`
namespace?: `x-${string}`

Service namespace, used to identify declare which namespace the service belongs to. It must start with x- as it is a custom namespace and will be used for custom headers, openc2 commands, etc.

`x-mytra`
release: string

Service release. Its recommended to use semantic versioning.

`1.0.0`
serviceGroupId?: string

Service group unique identification

`firehose`, `driver`
serviceId?: string

Service unique identification

`uplink-firehose`, `mqtt-driver`
tags?: string[]

List of string values that can be used to add service-level labels.

`["primary", "test"]`
version: string

Service version

`1`