-
Notifications
You must be signed in to change notification settings - Fork 640
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
[Docs] FlyteRemote code snippets need to be added to the remote access section #2769
Closed
2 tasks done
Tracked by
#2917
Labels
Comments
samhita-alla
added
documentation
Improvements or additions to documentation
untriaged
This issues has not yet been looked at by the Maintainers
labels
Aug 16, 2022
eapolinario
removed
the
untriaged
This issues has not yet been looked at by the Maintainers
label
Aug 19, 2022
50 tasks
Hello, can i work on this :) |
@Alcadeus0 are you still working on this one? If not I'd like to take over on it. |
you can go ahead and take over :) |
ok coolio. @samhita-alla can you re-assign when you get a chance? |
@samhita-alla thanks for assign. PR up to add the requested snippets to docs: flyteorg/flytesnacks#910 😎 |
eapolinario
pushed a commit
to eapolinario/flyte
that referenced
this issue
Dec 20, 2022
* add code snippets to remote access section closes flyteorg#2769 Signed-off-by: jerempy <[email protected]> * Update docs after feedback Signed-off-by: jerempy <[email protected]> Co-Authored-By: Samhita Alla <[email protected]> * More updates Signed-off-by: jerempy <[email protected]> Co-Authored-By: Samhita Alla <[email protected]> Signed-off-by: jerempy <[email protected]> Co-authored-by: Samhita Alla <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
The "Remote Access" section currently has
flytectl
commands to register and run flyte entities. FlyteRemote examples need to be appended to each of the doc pages to showcase accessing the backend programmatically through an API.Are you sure this issue hasn't been raised already?
Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: