When using any NIO Filesystem provider, Java will enumerate them all and try to create them.
Our CloudStorageFileSystemProvider will throw an exception if there is no GOOGLE_APPLICATION_CREDENTIALS environment variable (because then it can't find credentials). This seems reasonable at first but here this means that even if someone is not using gs:// at all, just by having our jar in the classpath they become unable to use other filesystem providers.
This issue shows a concrete instance, with example.
This suggests we need to allow CloudStorageFileSystemProvider to be created without credentials. We can fail later, when the user tries to get a CloudStorageFileSystem instance.
Sounds good?
cc: @jart, @mziccard
When using any NIO Filesystem provider, Java will enumerate them all and try to create them.
Our CloudStorageFileSystemProvider will throw an exception if there is no
GOOGLE_APPLICATION_CREDENTIALSenvironment variable (because then it can't find credentials). This seems reasonable at first but here this means that even if someone is not usinggs://at all, just by having our jar in the classpath they become unable to use other filesystem providers.This issue shows a concrete instance, with example.
This suggests we need to allow CloudStorageFileSystemProvider to be created without credentials. We can fail later, when the user tries to get a
CloudStorageFileSysteminstance.Sounds good?
cc: @jart, @mziccard