spring-cloud-gcp/Lobby

Artem Bilan

@artembilan

(I'm adding 1.3.x to the project page right now though)

Mike Eltsufin

@meltsufin

I think we can ignore 1.3.x for now

we really just need 1.2.x

Artem Bilan

@artembilan

Ah. OK! :smni

:smile:

Mike Eltsufin

@meltsufin

1.3.x is on Ilford, which will become 2.0

Marcin Grzejszczak

@marcingrzejszczak

I know why

There's no job to do that

https://github.com/spring-cloud/spring-cloud-jenkins-jobs/blob/master/src/main/groovy/org/springframework/jenkins/cloud/common/AllCloudJobs.groovy#L75

spring-cloud/spring-cloud-jenkins-jobs@660ba14

Marcin Grzejszczak

@marcingrzejszczak

Try again in 5 minutes (I've ran the new build)

Mike Eltsufin

@meltsufin

Thanks Marcin!!

Artem Bilan

@artembilan

Nice! Never understood Spring Cloud Contract

Mike Eltsufin

@meltsufin

it's working already!

Artem Bilan

@artembilan

But I got it: I just don't understand everything Marcin does

it's kinda magic! :wink:

Thank you very much for the help!

Marcin Grzejszczak

@marcingrzejszczak

No problem. We need to know that to build, we don't scan branches etc. so you need to provide it explicitly

Mike Eltsufin

@meltsufin

Makes sense.

Spencer Gibb

@spencergibb

@artembilan @elefeint

No. That's not how our support policy works

Actually we plan on supporting 2.3.x in Hoxton

Artem Bilan

@artembilan

Hm. No, SB-2.3 is going to be based on major Spring Data

And we saw yesterday some binary incompatibility between Spring Integration 5.3 and current Spring Cloud Stream

I don't know how many issues we may face when we pull minor SB release in point SC release

@spencergibb :arrow_double_up:

Mike Eltsufin

@meltsufin

@spencergibb So, one of the Hoxton SRs will switch to SB-2.3?

Spencer Gibb

@spencergibb

@meltsufin we hope to support 2.2 and 2.3 concurrently

Mike Eltsufin

@meltsufin

I see, but which version will spring-cloud-build import?

currently it's 2.2

Artem Bilan

@artembilan

We have made already a lot of braking changes in Spring Integration 5.3 to support Spring Data Neumann

So, I'm fully not sure how that going to work in Spring Cloud Hoxton when you pull Spring Boot 2.3 with those transitive dependencies

Mike Eltsufin

@meltsufin

https://seinfeldmemes.com/wp-content/uploads/2019/03/C396B2C0-6FCB-41FB-A9D2-1937D4CEB4C6.jpeg

Spencer Gibb

@spencergibb

@meltsufin it will be 2.3

Mike Eltsufin

@meltsufin

do you have an approximate timeline in mind?

Spencer Gibb

@spencergibb

after Hoxton.SR2
Spring Cloud milestones https://github.com/spring-cloud/spring-cloud-release/milestones?direction=asc&sort=due_date&state=open
and Boot milestones https://github.com/spring-projects/spring-boot/milestones?direction=asc&sort=due_date&state=open

end of Feb.

Mike Eltsufin

@meltsufin

got it, thanks

Spencer Gibb

@spencergibb

ilford branching will likely start end of this week or early next

skogs

@skogs

are there any Spring Cloud GCP apis to support creating and listing compute instances?
If not, seems I can use com.google.api.services.compute.Compute apis. Then, is there any
sharing possible between libs like credentials. thx!

Mike Eltsufin

@meltsufin

There aren't any integration for it. Your best bet is to probably use the client library: https://github.com/googleapis/java-compute

You should be able to use the credentials configured via spring-cloud-gcp-core-starter.

For

    AddressSettings addressSettings =
        AddressSettings.newBuilder()
            .setCredentialsProvider(FixedCredentialsProvider.create(myCredentials))

Just use the autowired CredentialsProvider.

...instead of the FixedCredentialsProvider.

skogs

@skogs

great, thanks

Serhat Soydan

@ssoydan-strands

Hi everyone,
I have a java-maven project which has a dependency - "spring-cloud-gcp-starter-pubsub"
I want to disable/enable pubsub with a property (not with a profile) but even when I think it is disabled, I see "failed to detect whether we are running on Google Compute Engine" info log.

I tried different properties like below but none of them seems to work. Do you know if any exist? With the dependency added, it always tries to connect.

spring.cloud.gcp.pubsub.enabled=false
spring.cloud.gcp.config.enabled=false
spring.cloud.gcp.security.iap.enabled=false

Elena Felder

@elefeint

This message comes from the core project attempting to automatically infer what authentication method to use. You have a couple of choices to suppress the attempt to connect to the metadata service: (1) you can explicitly specify credentials through properties or by registering your own bean of type CredentialsProvider (docs)

and (2) you can continue relying on autodiscovery, but specifically turn off the GCE check with an environment variable NO_GCE_CHECK=true (docs)

Mike Eltsufin

@meltsufin

@ssoydan-strands Can you try:
spring.autoconfigure.exclude=org.springframework.cloud.gcp.autoconfigure.core.GcpContextAutoConfiguration

Serhat Soydan

@ssoydan-strands

@elefeint NO_GCE_CHECK=true only cleared the log for "failed to detect whether we ....", but I can see more (at least 2) logs like below, so it is a partial workaround:

2020-01-29T15:49:08,655 INFO (1)main [ComputeEngineCredentials.java:257]: Failed to detect whether we are running on Google Compute Engine.
2020-01-29T15:49:08,656 WARN (1)main [DefaultCredentialsProvider.java:128]: No core credentials are set. Service-specific credentials (e.g., spring.cloud.gcp.pubsub.credentials.*) should be used if your app uses services that require credentials.
2020-01-29T15:49:08,698 INFO (1)main [GcpContextAutoConfiguration.java:75]: The default project ID is XXX

@meltsufin it seems that your workaround is working but it is really hard to guess and ugly to find which class to exclude. I would expect the same behaviour after -> spring.cloud.gcp.pubsub.enabled=false

Mike Eltsufin

@meltsufin

yeah we already have an issue to add spring.cloud.gcp.core.enabled prop

Where communities thrive

People

Repo info

Activity