-
Notifications
You must be signed in to change notification settings - Fork 672
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] move aws scheduler docs to the legacy section #4513
Comments
🤖 It seems like you've got this under control, if you want help or have specific questions, let me know what I can do for you! This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research. Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant. If you want to continue the conversation, start your reply with @dosu-bot. |
Hi, I would like to work on this |
Hi! @samhita-alla, this is the github repo for flyte docs, right? |
Hi! @samhita-alla, this is my PR: #5826 |
Hi! @samhita-alla, this is my PR: #5826, can u pls review it |
@davidmirror-ops @samhita-alla can u pls review my PR: : #5826 |
Could you please share any suggestions or changes that might be required? If everything looks good from your end, I believe we can go ahead and close this issue. |
@davidmirror-ops @samhita-alla Could you please share any suggestions or changes that might be required? |
Hi, @samhita-alla, can u pls review my PR: #5826 |
Description
delete documentation related to AWS scheduler configuration, as the flyte native scheduler should just work.
reference slack thread: https://discuss.flyte.org/t/15852550/hi-team-i-have-created-a-simple-test-flyte-scheduler-using-b#929e7edd-c801-4dbb-bdbf-61cb36903727
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: