Getting Started with Security updates #45646
Merged
+10
−20
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
quarkus-bot
bot
added
area/docstyle
|
🙈 The PR is closed and the preview is expired. |
This comment has been minimized.
This comment has been minimized.
rolfedh
reviewed
Jan 16, 2025
rolfedh
reviewed
Jan 16, 2025
sberyozkin
force-pushed
the
getting_started_security_update
branch
from
366b286 to
9e79265
Compare
gastaldi
approved these changes
Jan 16, 2025
Status for workflow
|
gsmet
approved these changes
Jan 16, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As Martin Ocenas rightly pointed out, the configuration advice is confusing, first we suggest using prod level DB properties without
%prodwhich causesmvn quarkus:devfailure and then recommend using@prod. I've done minor updates to fix it, and also other minor updates recommended by Martin