The job scheduler server for application jobs
Request from application container URLs
POST
http://<job-name>:8080/api/v1/jobs
- start a new jobGET
http://<job-name>:8080/api/v1/jobs
- get a job listGET
http://<job-name>:8080/api/v1/jobs/<job-name>
- get a job statusDELETE
http://<job-name>:8080/api/v1/jobs/<job-name>
- delete a jobPOST
http://<job-name>:8080/api/v1/jobs/<batch-name>/stop
- stop a batchPOST
http://<job-name>:8080/api/v1/batches
- start a new batchGET
http://<job-name>:8080/api/v1/batches
- get a batch listGET
http://<job-name>:8080/api/v1/batches/<batch-name>
- get a batch statusDELETE
http://<job-name>:8080/api/v1/batches/<batch-name>
- delete a batchPOST
http://<job-name>:8080/api/v1/batches/<batch-name>/stop
- stop a batchPOST
http://<job-name>:8080/api/v1/batches/<batch-name>/jobs/<job-name>/stop
- stop a batch job
You need Go installed. Run make bootstrap
to install required tools.
We follow the semantic version as recommended by go.
radix-job-scheduler
has three places to set version
-
apiVersionRoute
inrouter/server.go
andBasePath
indocs/docs.go
- API version, used in API's URL -
Version
indocs/docs.go
- indicates changes in radix-job-scheduler logic - to see (e.g in swagger), that the version in the environment corresponds with what you wantedRun following command to update version in
swagger.json
make swagger
-
If generated file
swagger.json
is changed (methods or structures) - copy it to the public site
By default Info
and Error
messages are logged. This can be configured via environment variable LOG_LEVEL
(pods need to be restarted after changes)
LOG_LEVEL=ERROR
- log onlyError
messagesLOG_LEVEL=INFO
or not set - logInfo
andError
messagesLOG_LEVEL=WARNING
or not set - logInfo
,Warning
andError
messagesLOG_LEVEL=DEBUG
- logDebug
,Warning
,Info
andError
messages
By default swagger UI
is not available. This can be configured via environment variable USE_SWAGGER
USE_SWAGGER=true
- allows to use swagger UI with URL<api-endpoint>/swaggerui
We use gomock to generate mocks used in unit test. https://github.com/golang/mock
You need to regenerate mocks if you make changes to any of the interfaces in the code, e.g. the job Handler interface
Run make mocks
to regenerate mocks
We follow the semantic version as recommended by go.
-
tag
in git repository (inmain
branch)Run following command to set
tag
(with corresponding version)git tag v1.0.0 git push origin v1.0.0
Want to contribute? Read our contributing guidelines
This is how we handle security issues