-
Notifications
You must be signed in to change notification settings - Fork 39
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
Feature Request: nflow explorer capable of querying all executor groups #647
Comments
I think this is a very good and useful feature. |
i was unsure of the api to "get executor groups" my initial thought was a config param in explorer (list of executor names). this was because you may want to have "hidden" executors. i may be over thinking it and a dynamic list from the api would probably be more practical |
@gmokki ive started on this feature,
does the above sound about right ? or would it be better to change the default and not have a system setting for this ? |
enhanced the create workflow to also have an executor selection display the executor group under the details enhance executors view to show all some css changes to keep all search fields on the same line now with the extra field @efonsell @gmokki |
Sorry for taking so long to comment - the process is to create MR. There was some recent work on Explorer so you may have some conflicts in your branch, sorry about that as well. In general, I think the screenshots look very good. |
Hi,
Looking at the possibility of extending the nflow api, such that the executor group can be sent from explorer to be "all" or a specific executor group. the thought of this is that.
you can have two executor groups on the same database
ie nflow_one and nflow_two
from explorer you can select an executor group to view, at the moment you would need two nflow explorer instances connecting to the API for each executor group. but this could be useful to have one api/explorer to service both
the code in reference comes from the executor Dao in
to get this through would be an additional @RequestParam to the rest api in WorkflowInstanceResource.
then on nflow explorer, a new config to have a drop down list in the nav bar to select the executor group
The text was updated successfully, but these errors were encountered: