Open zeryx opened 1 year ago
Hi, I am interested in this issue, please give me a chance.
😊 "I'd be delighted to work on this issue, @zeryx ! Could you please assign it to me?"
@samhita-alla @zeryx I am interested in doing this issue So kindly assign me this issue Thank You : )
Please go ahead and create a PR, @TechWizard9999, @Kota-Karthik. We will consider whoever creates a PR first on a first-come, first-serve basis.
@samhita-alla I'm interested in working on this issue. If I can make the feature, can I create a PR?
@samhita-alla I'm interested in working on this issue. If I can make the feature, can I create a PR?
She means that the first pr will be accepted!
@samhita-alla , I have raised a PR for this, I request you to please have a look at it and let me know if the changes are valid
Hello 👋, this issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will engage on it to decide if it is still applicable. Thank you for your contribution and understanding! 🙏
Describe the feature/command for FlyteCTL
pyflyte register today does not have any mechanism for providing an organized output containing the registered workflow/task/launchplan names, and their versions.
This request would be to provide a --output=X flag that can denote how the output should be formatted. This could be by default =json, and =yaml.
Provide a possible output or UX example
I should be able to run
pyflyte register --remote somewf_dir --output=json
and the following output.json file should exist in the repoAre you sure this issue hasn't been raised already?
Have you read the Code of Conduct?