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

refactor: Kubernetes extension now uses quarkus. #7339

Merged
merged 1 commit into from
Feb 23, 2020

Conversation

iocanel
Copy link
Contributor

@iocanel iocanel commented Feb 21, 2020

This pull request adds the quarkus. prefix to kubernetes related properties.
For backwards compatibility it still supports the prefix-less properties.

The change is also applied in the docs & tests.

gsmet
gsmet previously requested changes Feb 21, 2020
Copy link
Member

@gsmet gsmet left a comment

Choose a reason for hiding this comment

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

I don't see any config classes there? Don't you have a ton of warnings about unused properties?

@iocanel
Copy link
Contributor Author

iocanel commented Feb 21, 2020

I don't see any config classes there? Don't you have a ton of warnings about unused properties?

The change is about the properties that are being sent pass-through to dekorate, so there is no config class for them.

@gsmet
Copy link
Member

gsmet commented Feb 21, 2020

Yes, but if you have quarkus. properties without config classes, IIRC, you get some warnings.

/cc @geoand

@iocanel
Copy link
Contributor Author

iocanel commented Feb 21, 2020

I see.
Yeah upon closer inspection I do get those warnings.

@geoand
Copy link
Contributor

geoand commented Feb 21, 2020 via email

@iocanel iocanel force-pushed the kubernetes-properties branch 3 times, most recently from 2bdd467 to f8fdbac Compare February 23, 2020 00:46
@iocanel
Copy link
Contributor Author

iocanel commented Feb 23, 2020

@angelozerr: FYI: This pull request brings in proper quarkus config classes for all properties.

@geoand
Copy link
Contributor

geoand commented Feb 23, 2020

That is absolutely great! Thanks for the hard work that you put into this! I'll have some time later on today to go over it

Copy link
Contributor

@geoand geoand left a comment

Choose a reason for hiding this comment

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

I added a bunch of small comments.

FWIW I think this work is great and is great step forward for the user friendliness of the kubernetes extension!
If you don't have time to take care of this comments yourself, please and let me know and I can fix them myself later on today so we can get this in ASAP

@iocanel iocanel force-pushed the kubernetes-properties branch from f8fdbac to e492c8b Compare February 23, 2020 16:48
@geoand
Copy link
Contributor

geoand commented Feb 23, 2020

When done taking care of the comments, can you please resolve them?

Thanks

@iocanel iocanel force-pushed the kubernetes-properties branch from e492c8b to 6e2bf5a Compare February 23, 2020 18:06
@geoand
Copy link
Contributor

geoand commented Feb 23, 2020

The CI failure is totally unrelated, but in any case CI will run again when the next round of fixes comes in

@iocanel
Copy link
Contributor Author

iocanel commented Feb 23, 2020

@geoand: There are no pending fixes. So, we may need to rebase/kick again?

@geoand
Copy link
Contributor

geoand commented Feb 23, 2020

@iocanel I don't think all of the comments have been addressed. I think that you have missed the middle ones (that github probably grouped under xxx hidden conversations)

@geoand
Copy link
Contributor

geoand commented Feb 23, 2020

Please ping me once they are addressed so I can review and merge ASAP - it would be great to have this in for 1.3.CR1

@iocanel iocanel force-pushed the kubernetes-properties branch from 6e2bf5a to 2d97a42 Compare February 23, 2020 19:30
@iocanel
Copy link
Contributor Author

iocanel commented Feb 23, 2020

Please ping me once they are addressed so I can review and merge ASAP - it would be great to have this in for 1.3.CR1

I think that now even the middle items have been addressed.

Copy link
Contributor

@geoand geoand left a comment

Choose a reason for hiding this comment

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

This is great step forward. Any improvements can definitely be made in the time between CR1 and Final

@geoand geoand dismissed gsmet’s stale review February 23, 2020 19:37

Proper config objects have been created

@geoand geoand added this to the 1.3.0 milestone Feb 23, 2020
@geoand geoand merged commit 3699188 into quarkusio:master Feb 23, 2020
@angelozerr
Copy link

@angelozerr: FYI: This pull request brings in proper quarkus config classes for all properties.

Thanks @iocanel for this great info. As you are using ConfigRoot it should work without developping something. But the question is to we need to continue to provide kubernetes.* properties in the completion?

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.

4 participants