Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use correct default config source name to check Kubernetes config disabled #35696

Merged
merged 1 commit into from Sep 4, 2023

Conversation

radcortez
Copy link
Member

@quarkus-bot
Copy link

quarkus-bot bot commented Sep 2, 2023

✔️ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

@geoand geoand merged commit 8876145 into quarkusio:main Sep 4, 2023
19 checks passed
@quarkus-bot quarkus-bot bot added this to the 3.4 - main milestone Sep 4, 2023
@cescoffier
Copy link
Member

@radcortez do you know if 3.2 is affected? If so, we need to backport it.

@@ -84,7 +84,7 @@ Iterable<ConfigSource> getConfigSources(final KubernetesConfigSourceConfig confi

private boolean isExplicitlyDisabled(ConfigSourceContext context) {
ConfigValue configValue = context.getValue("quarkus.kubernetes-config.enabled");
if (AbstractRawDefaultConfigSource.NAME.equals(configValue.getConfigSourceName())) {
if ("DefaultValuesConfigSource".equals(configValue.getConfigSourceName())) {
Copy link
Member

Choose a reason for hiding this comment

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

Should it be a constant? IS the other constant still in use?

Copy link
Contributor

Choose a reason for hiding this comment

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

My understanding is that this will go away when the TODO is implemented

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes, I need to improve this a bit. This was a migration as is, so I didn't want to introduce other changes as well. As for the constant, the source is provided by SR Config, so I prefer to add the constant there.

@radcortez
Copy link
Member Author

@radcortez do you know if 3.2 is affected? If so, we need to backport it.

For 3.2 no. This was introduced with #34457. The issue is that the Default source for mappings have a different name, so the behaviour was not the same.

@gsmet gsmet modified the milestones: 3.4 - main, 3.3.2 Sep 4, 2023
@radcortez radcortez deleted the fix-35673 branch September 8, 2023 10:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Kubernetes secret not read anymore in 3.3
4 participants