Skip to content

ernestio/service-store

Repository files navigation

Service Store

master: CircleCI
develop: CircleCI

It manages all ernest environment & build storage through a public Nats API

Installation

make deps
make install

Running Tests

make deps
make test

Endpoints

You have available the nats endpoints:

###environment.get It receives as input a valid environment with only the id or name as required fields. It returns a valid environment.

###environment.del It receives as input a valid environment with only the id as required field. And it deletes the row if it can find it.

###environment.set It receives as input a valid environment with id or not, and it will create or update the environment with the given fields.

###environment.find It receives as input a valid service, and it will do a search on the database with the given fields.

###build.get It receives as input a valid build with only the id or name as required fields. It returns a valid build.

###build.del It receives as input a valid build with only the id as required field. And it deletes the row if it can find it.

###build.set It receives as input a valid build with id or not, and it will create or update the build with the given fields.

###build.find It receives as input a valid service, and it will do a search on the database with the given fields.

###build.get.mapping It receives as input a valid environment with only the id or name as required fields. It returns a valid environment.

###build.set.mapping It receives as input a valid environment with id, and it will update the environment with the mapping field.

###build.get.definition It receives as input a valid environment with only the id or name as required fields. It returns a valid environment definition.

###build.set.definition It receives as input a valid environment with id, and it will update the environment with the definition field.

Contributing

Please read through our contributing guidelines. Included are directions for opening issues, coding standards, and notes on development.

Moreover, if your pull request contains patches or features, you must include relevant unit tests.

Versioning

For transparency into our release cycle and in striving to maintain backward compatibility, this project is maintained under the Semantic Versioning guidelines.

Copyright and License

Code and documentation copyright since 2015 ernest.io authors.

Code released under the Mozilla Public License Version 2.0.

About

Ernest service management service.

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages