-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Review and define agent bootstrapper events #5266
Labels
kind/task
Internal things, technical debt, and to-do tasks to be performed.
Comments
voievodin
added
the
kind/task
Internal things, technical debt, and to-do tasks to be performed.
label
Jun 2, 2017
skabashnyuk
added
sprint/current
status/open-for-dev
An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it.
team/platform
labels
Jun 8, 2017
I reviewed bootstrapper events, after they approved here i will change the spec. Bootstrapper events
Agents events
|
@gazarenkov, @garagatyi, @dkuleshov, @mshaposhnik WDYT? |
voievodin
changed the title
Review and define agent installer events
Review and define agent bootstrapper events
Jun 12, 2017
LGTM |
Added events to the spec |
voievodin
removed
the
status/open-for-dev
An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it.
label
Jun 12, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Agent installation spec defines agent bootstrapper events(see Agent lifecycle events).
According to new generation SPI, defined events - do not provide enough information. For example each agent event should provide machine identifier as well as its own identifier, it can be either structured id like
or it can be a path like
or it can be a machine id
Another point is that the format of events names should fit the concept of workspace master events.
The DOD of the issue is to provide a list of jsonrpc2.0 events needed to be produced by bootstrapper,
which allows to develop java client & installer separately.
The text was updated successfully, but these errors were encountered: