Channels
datahub-flyte
scipy-2023-workshop
flyte-school
agent-support-memverge
flyte-build
flyte-users-berlin
scipy-2023-sprint
auth
flyte-bazel
large-language-models
contribute
bioinformatics-computational-biology
great-content
in-flyte-conversations
flyte-on-gcp
show-and-tell
shameless-promotion
linkedin-flyte
random
deployment
hacktoberfest-2023
flyte-github
feature-discussions
linen-test
flytelab
flytekit-java
integrations
ray-on-flyte
conference-talks
release
flyte-ui-ux
workflow-building-ui-proj
writing-w-sfloris
jobs
hacktoberfest-2022
torch-elastic
flyte-console
engineeringlabs
helsing-flyte
flyte-documentation
konan-integration
databricks-integration
ray-integration
wg-gpu-types
flytekit
ecosystem-unionml
scipy-2022-sprint
announcements
ask-the-community
flyte-deployment
introductions
events
Powered by
#contribute
Title
# contribute
b
Byron Hsu
04/11/2023, 12:12 AM
IIRC, after
this change
, we don’t need to explicitly import
awscli
in the image to pull the data from s3 right?
@Ketan (kumare3)
y
Yee
04/11/2023, 12:17 AM
correct
p
Pradithya Aria Pura
04/12/2023, 1:52 PM
Nice! Will it be backported to 1.2.X? Does it mean flytekit now transitively depends on corresponding blob store (s3, gcs, etc) ?
k
Ketan (kumare3)
04/12/2023, 2:25 PM
Yes
Using fsspec
Also you have streaming apis
2 Views
Post