Disable service authentication

[fabrii]

It seems that the credentials file is mandatory. If we don't provide one, the application cannot start.

In my case, I am using Google Storage to persist files. In some dev environments I want to save the files directly to the filesystem without providing a ".json" file with credentials.

Is there any way of doing this?

Thanks!

[loicmathieu]

It's a little more complexe, see https://github.com/quarkiverse/quarkus-google-cloud-services#authenticating-to-google-cloud

Your issue is that you want to use Storage in some env and something else on other env.
And as soon as you add the storage dependency, a Storage CDI bean is produced that mandates the authentication.

The issue is that somewhere inside your code you inject the Storage bean, and this triggers the auth.

To workaround this, you can provide an alternative bean that mock the Storage bean and will be injected instead of the real one.

Another solution would be to have a CDI producer that will conditionaly produce a StorageFileService or a LocalFileService based on a config property. The StorageFileService would wrap the Storage object so that if not produced, the Storage bean will not be initialized as not injected anywhere.

[loicmathieu]

@fabrii do you successfully workaround the issue with my explaintations ? Can I close this issue now ?

[fabrii]

Hi @loicmathieu.

I couldn't workaround the issue.
What I had in mind when reporting the issue was creating a property similar like this:

quarkus.google.cloud.enabled=false (optional, true by default)

And use that property internally to disable the initialization of the component.

If this approach is not correct, you can close the issue.

Thanks!

[fabrii]

We managed to solve it in an easier way. We moved the @Inject Storage to a @RequestScoped bean.
That bean is only created when the methods are invoked, so no Storage automatic initialization.