It should be possible to use non-system level variables when configuring VFS features. This is because we don't expose any IVariables objects into the various HopVfs calls that resolve FileObjects, InputStream/OutputStream and so on.
Important features should be configurable through a standard environment configuration file to match our lifecycle management vision.
We should be able to tie the authentication of VFS file systems against the Authentication Provider plugins which are already present in Apache Hop but go unused. For example if we have a secure FTP target and we want to authenticate using a secure key we should be able to provide that key and use that to authenticate against a certain hostname.
It should be possible to authenticate differently to several systems in the same project or environment. For example it should be possible to authenticate to different hdfs:// servers at the same time or use multiple Amazon s3:// accounts at the same time. This would allow us to transfer data from one account to another for example.
It should be possible to create symbolic links through our VFS driver usage where we map one folder to another hiding the implementation details.