Skip to content
This repository has been archived by the owner on Jul 23, 2020. It is now read-only.

Populate new fabric8-services/fabric8-starter repository with sample service #3720

Open
stooke opened this issue Jun 1, 2018 · 3 comments
Open

Comments

@stooke
Copy link
Collaborator

stooke commented Jun 1, 2018

This repository contains a small skeleton Fabric8 service that starts and provides a few required endpoints for service readines and metrics. Wherever possible, it uses fabric8-services/fabric8-common packages to implement functionality.

Contents of this repository are anticipated to include:

Build

Dependency management
Goa code generation
Docker
Tests
common target names
Database

Database migration
local Docker instance
Dev tools

Debugging
Dev / prod-preview / production
Documentation

What this template service actually does and how it's put together
How this service uses the common code
Coding idioms encouraaged within fabric8-services

@stooke stooke self-assigned this Jun 1, 2018
@stooke
Copy link
Collaborator Author

stooke commented Jun 1, 2018

@aslakknutsen has a suggestion for various levels of app - hopefully the repo will allow this:

  1. Basic service

    1. build scripts
    2. docker file(s)
  2. Basic k8 service

    1. readiness endpoint
    2. health endpoint
    3. json based console logging
    4. error reporting to sentry
    5. metrics exposure for prometheus
    6. ops abillity (gops) for runtime inspection
    7. tracing ability via e.g. Opentracing (comming)
    8. deployment templates
    9. env configuration
  3. Basic osio service

    1. api http endpoint
    2. service http clients
    3. event bus connection for publish / receive
  4. Osio service

    1. Service login with Auth
    2. Public keys from Auth (with auto refresh)
  5. Osio 'some what common'

    1. Cluster API (with auto refresh)
    2. Cluster Token Decode
  6. Osio service business logic

    1. xxx, what ever the 'thing' is intended to do

@joshuawilson
Copy link
Member

Please add labels. Is this a task or user-story?

@stooke
Copy link
Collaborator Author

stooke commented Jun 1, 2018

I think it's a task.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants