-
Notifications
You must be signed in to change notification settings - Fork 682
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 example throws an error #4351
Comments
can you confirm the version of flytekit ? |
Ok, I was using 1.9.1. I just switched to 1.10. I'm running a sandbox cluster so I used this:
Once I explicitly indicate it:
It works. I wasn't able to find how to indicate a default project/domain in the config file . cc @samhita-alla do you think this is something we should add to the docs? Am I missing a step so |
@davidmirror-ops, the default project and domain must be specified in the FlyteRemote config. Otherwise, you could also specify the project and domain during fetching or execution. Does that make sense? |
I think the error message should look better |
@samhita-alla It makes sense. The problem is that this is not mentioned in the example, but it's written so the reader understands that |
@davidmirror-ops, in that case, we need to update flyte remote docs. |
Description
While runnning the FlyteRemote example locally, the result is the following error message:
There's no reference to look further into FlyteRemote Config. A manual search leads to the FlyteRemote page but even adding explicitly the config like this:
remote = FlyteRemote(config= Config.for_endpoint(endpoint="localhost:30088", config_file="$HOME/.flyte/config.yaml"),default_project="flytesnacks",default_domain="development")
leads to an error:
FileNotFoundError: [Errno 2] No such file or directory: '$HOME/.flyte/config.yaml'
I'm sure there's something really simple I'm missing but it's nowhere explained in the docs.
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: