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.

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

Remove the metadata command from the beeflow client #979

Open
rstyd opened this issue Dec 13, 2024 · 0 comments · May be fixed by #982
Open

Remove the metadata command from the beeflow client #979

rstyd opened this issue Dec 13, 2024 · 0 comments · May be fixed by #982
Assignees
Labels
core Core BEE functionality that must exist

Comments

@rstyd
Copy link
Collaborator

rstyd commented Dec 13, 2024

@jtronge Added the metadata command to the beeflow client to support his GUI client. We deprecated the GUI client earlier this year, and the problem the metadata command was intended to solve (figuring out which bolt port belongs to which workflow). Isn't an issue now since all workflows share a bolt port due to @kabir-vats refactor of the GDB. I propose we remove command and the associated resource in beeflow/wf_manager/resources.

@rstyd rstyd added the core Core BEE functionality that must exist label Dec 13, 2024
@arhall0 arhall0 self-assigned this Dec 19, 2024
@arhall0 arhall0 linked a pull request Dec 20, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core Core BEE functionality that must exist
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants