You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Setting spring.cloud.gcp.core.enabled=false causes the application to fail on startup because LoggingWebMvcConfigurer cannot be instantiated since there is no GcpProjectIdProvider bean.
I would expect disabling GCP core to also disable Cloud Logging; however, this also requires setting spring.cloud.gcp.logging.enabled=false to prevent StackDriverLoggingAutoConfiguration from being processed.
I also noticed that LoggingWebMvcConfigurer doesn't even make use of the provided GcpProjectIdProvider so it's not clear to me why it's even needed.
Sample
Create a Spring Boot application
Add spring-boot-starter-web and spring-cloud-gcp-starter-logging dependencies to the pom
Add spring.cloud.gcp.core.enabled=false to application.properties
The text was updated successfully, but these errors were encountered:
Describe the bug
Setting
spring.cloud.gcp.core.enabled=false
causes the application to fail on startup becauseLoggingWebMvcConfigurer
cannot be instantiated since there is noGcpProjectIdProvider
bean.I would expect disabling GCP core to also disable Cloud Logging; however, this also requires setting
spring.cloud.gcp.logging.enabled=false
to preventStackDriverLoggingAutoConfiguration
from being processed.I also noticed that
LoggingWebMvcConfigurer
doesn't even make use of the providedGcpProjectIdProvider
so it's not clear to me why it's even needed.Sample
spring-boot-starter-web
andspring-cloud-gcp-starter-logging
dependencies to the pomspring.cloud.gcp.core.enabled=false
toapplication.properties
The text was updated successfully, but these errors were encountered: