Skip to content
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.

Sign up for GitHub

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

Jump to bottom

document async nature of engine ops #297

Open
pferrel opened this issue Apr 9, 2021 · 2 comments
Open

document async nature of engine ops #297

pferrel opened this issue Apr 9, 2021 · 2 comments
Assignees
@pferrel
Labels
enhancement
Milestone
future

Comments

@pferrel
Copy link
Collaborator

pferrel commented Apr 9, 2021

response to engine add, for instance, only means the "job" of adding has been accepted. It does not mean engine params are validated -- as of etcd version.
@pferrel
Copy link
Collaborator Author

pferrel commented Apr 9, 2021

the engine ops are now async with the REST calls so document this. For instance is hctl status engines does not return the correct params, then the logs must be searched for the engine op error, it is not retrievable via the API

@pferrel pferrel self-assigned this Apr 9, 2021
@pferrel pferrel added this to the future milestone Apr 9, 2021
@pferrel
Copy link
Collaborator Author

pferrel commented Apr 9, 2021

only applies to Harness 1.0+

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pferrel pferrel

Labels
enhancement
Projects
None yet
Milestone
future
Development

No branches or pull requests
1 participant
@pferrel