Skip to content

Conversation

aureamunoz
Copy link
Member

I think I missed that when adding the spring-security extension.
WDYT @geoand @michalszynkiewicz @gsmet ?
Related to #5225

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.

Looks good, thanks for taking care of that, I added a minor comment.

metadata:
keywords:
- "spring-security"
- "spring"
Copy link
Member

Choose a reason for hiding this comment

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

Maybe add security as a keyword too.

Copy link
Member Author

Choose a reason for hiding this comment

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

yep, good idea.

Copy link
Member

Choose a reason for hiding this comment

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

I just force-pushed an amended commit with the security keyword added. Let's wait for CI.

@gsmet
Copy link
Member

gsmet commented Nov 25, 2019

@aloubyansky @maxandersen any chance we could fail if one extension is missing the metadata?

@aloubyansky
Copy link
Member

We surely can fail if no descriptor is provided. OTOH, I like the idea of not requiring a metadata and generating the basic one as the default. It'd be one of the requirements however to have a detailed enough metadata to be accepted in the platform.

@gsmet
Copy link
Member

gsmet commented Nov 25, 2019

@aloubyansky any chance it could be optional and we could enforce that in the Quarkus and Platform builds?

@aloubyansky
Copy link
Member

aloubyansky commented Nov 25, 2019 via email

@gsmet
Copy link
Member

gsmet commented Nov 25, 2019

@aloubyansky I think if the file is there, people will review it properly. But I'm not sure they will think of it if it's missing (we have a good example here).

@gsmet gsmet force-pushed the spring-security-metadata branch from 9942575 to b5ac769 Compare November 25, 2019 12:36
@gsmet gsmet added this to the 1.1.0 milestone Nov 25, 2019
@gsmet gsmet added the triage/waiting-for-ci Ready to merge when CI successfully finishes label Nov 25, 2019
@maxandersen
Copy link
Member

we definitely could do a "platform-lint" that could warn/errror on issues; especially something we could enforce in platform and at least in quarkus hosted extensions.

@gsmet gsmet merged commit 40981d8 into quarkusio:master Nov 25, 2019
@gsmet
Copy link
Member

gsmet commented Nov 25, 2019

Merged, thanks!

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

Labels

triage/waiting-for-ci Ready to merge when CI successfully finishes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants