Skip to content

Initialize ConfigClientProperties instead of using whats in bootstrap.#2282

Merged
ryanjbaxter merged 1 commit intospring-cloud:3.1.xfrom
ryanjbaxter:initialize-configclientpropertiesalways
Jun 16, 2023
Merged

Initialize ConfigClientProperties instead of using whats in bootstrap.#2282
ryanjbaxter merged 1 commit intospring-cloud:3.1.xfrom
ryanjbaxter:initialize-configclientpropertiesalways

Conversation

@ryanjbaxter
Copy link
Copy Markdown
Contributor

Fixes #2281

assertThat(resource.getProperties().getUri()).containsExactly(locationUri.split(","));
}

@Test
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We are no longer using the properties stored in the bootstrap context, this test is not valid

ConfigDataLocation.of("configserver:http://urlNo2"), mock(Profiles.class));
assertThat(resources1).hasSize(1);
assertThat(resources2).hasSize(1);
verify(bootstrapContext, times(2)).get(eq(ConfigClientProperties.class));
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We are no longer making this call

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ConfigServerConfigDataLocationResolver binds ConfigClientProperties before classpath application properties have been loaded

2 participants