Has there ever been any thought given to aliasing ...
# flyte-support
g
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.
f
This the uris are static because moving data is weird and hard and not guaranteed to work. This is why aliasing is not supported. If you want invariant methods just implement your own protocol in the data layer
g
Will have a look around - thanks
The question is coming up from some infra folks who have 2 reqs: • supporting lift and shift • multi-region DR I'm trying to figure out a reasonable way to tackle this