[Docs] use gitsha

flyteorg · Oct 12, 2024 · 719db18 · 719db18
1 parent 98a2301
commit 719db18
Showing 1 changed file with 5 additions and 5 deletions.
diff --git a/docs/user_guide/concepts/main_concepts/data_management.rst b/docs/user_guide/concepts/main_concepts/data_management.rst
@@ -59,7 +59,7 @@ data from the configured object-store paths. These paths are completely customiz
 * To override the ``RawOutput`` path (prefix in an object store like S3/GCS),
     you can specify an alternate location when invoking a Flyte execution, as shown in the following screenshot of the LaunchForm in FlyteConsole:
 
-  .. image:: https://raw.githubusercontent.com/flyteorg/static-resources/main/flyte/concepts/data_movement/launch_raw_output.png
+  .. image:: https://github.com/flyteorg/static-resources/blob/ddec386ab74897e3c09d89fdaf305e77a2ecc52c/flyte/concepts/data_movement/launch_raw_output.png
 
 * In the sandbox, the default Rawoutput-prefix is configured to be the root of the local bucket.
     Hence Flyte will write all the raw data (reference types like blob, file, df/schema/parquet, etc.) under a path defined by the execution.
@@ -148,13 +148,13 @@ We could use fast metadata stores to speed up data movement or exploit locality.
 Between Flytepropeller and Tasks
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-.. image:: https://raw.githubusercontent.com/flyteorg/static-resources/main/flyte/concepts/data_movement/flyte_data_movement.png
+.. image:: https://github.com/flyteorg/static-resources/blob/ddec386ab74897e3c09d89fdaf305e77a2ecc52c/flyte/concepts/data_movement/flyte_data_movement.png
 
 
 Between Tasks
 ~~~~~~~~~~~~~
 
-.. image:: https://raw.githubusercontent.com/flyteorg/static-resources/main/flyte/concepts/data_movement/flyte_data_transfer.png
+.. image:: https://github.com/flyteorg/static-resources/blob/ddec386ab74897e3c09d89fdaf305e77a2ecc52c/flyte/concepts/data_movement/flyte_data_transfer.png
 
 
 Bringing in Your Own Datastores for Raw Data
@@ -233,8 +233,8 @@ This example shows how to access an existing file in a MinIO bucket from the Fly
 
 First task output metadata:
 
-.. image:: https://raw.githubusercontent.com/flyteorg/static-resources/main/flyte/concepts/data_movement/flyte_data_movement_example_output.png
+.. image:: https://github.com/flyteorg/static-resources/blob/ddec386ab74897e3c09d89fdaf305e77a2ecc52c/flyte/concepts/data_movement/flyte_data_movement_example_output.png
 
 Second task input metadata:
 
-.. image:: https://raw.githubusercontent.com/flyteorg/static-resources/main/flyte/concepts/data_movement/flyte_data_movement_example_input.png
+.. image:: https://github.com/flyteorg/static-resources/blob/ddec386ab74897e3c09d89fdaf305e77a2ecc52c/flyte/concepts/data_movement/flyte_data_movement_example_input.png