. Maybe also merge https://github.com/flyteorg/flytecopilot/pull/28 which looks fine. Then I can rebase my PR on top of these. If you could enable my GitHub user to trigger CI workflows that would also be great, my GH user is https://github.com/convexquad. @Haytham Abuelfutuh @Ketan (kumare3)
? • Is it best practice to assign a SA/IAM role for each task, or reuse the same identity on a workflow basis? • What should be configured in
needs to access both data and train, do you still recommend this structure and reference everything in
relative root? Probably not explaining the idea that well, but interested in what you think is the best practice with respect to workflows and relative imports/access to other folders containing data/code important to your project.
├── Dockerfile ├── data │ └── some_folder_with_data ├── train │ ├── train.py ├── docker_build_and_tag.sh ├── flyte │ ├── __init__.py │ └── workflows │ ├── __init__.py │ └── workflow.py ├── flyte.config └── requirements.txt
Robinson N. Costa
it doesn’t find it. Any idea why?
docker pull <http://cr.flyte.org/flyteorg/flyteconsole-release:v0.19.3|cr.flyte.org/flyteorg/flyteconsole-release:v0.19.3>