New RunLLM response generated: >>>*# Question* Has there ever been any thought given to aliasing blob paths inside of compiled protobuf? Either through relative URL or some other mechanism where flyte maintains a map of how to indirect from alias -> real blob? I brought up a question about how to approach migrating data from one bucket -> another ... this is another idea around making the location more flexible so that data doesn't need to be rewritten during a migration. # Answer Yes, there has been discussion around aliasing blob paths in Flyte. According to the RFC for Artifact service, Flyte is considering the use of aliases for artifacts, which can help manage versions and facilitate easier data migrations. The idea is to allow artifacts to have additional metadata, including aliases, which can be used to reference the latest version or other specific versions of an artifact. This would enable more flexible data management without needing to rewrite data during migrations. Would you like more detail on how this aliasing mechanism might be implemented or its current status? Sources: - RFC for Artifact service Slack Link https://flyte-org.slack.com/archives/CP2HDHKE1/p1722370239.268609 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.