Skip to content

Register / health check microservice #11

@Relrin

Description

@Relrin

In actual moment of time the matchmaking microservice experiencing a lack of required functionality, that must be implemented by default for each existing microservice in general:

  • Registering in Auth/Auth microservice after it was started, with specifiying the required permissions:
{
    'name': 'matchmaking',
    'version': '0.1.0', 
    'permissions': [
        {
            'codename': 'matchmaking.games.retrieve',
            'description': 'Can be added or received the state of the search',
        },
        {
            'codename': 'matchmaking.games.update',
            'description': 'Can update the state of the search',
        },
        {
            'codename': 'matchmaking.games.search.cancel',
            'description': 'Can cancel searching match',
        },
    ]
}
  • Health check endpoint, that accepts GET methods and returns status 200 without any body inside

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions