-
Notifications
You must be signed in to change notification settings - Fork 47
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
Update FeatureUtility command to include new verify option #6649
Comments
Update FeatureUtility command-new verify option-1 #6649
Hi Sarah, The suggested changes have been made to the documentation. Draft links:
Please review the changes. Regards, CC @dmuelle |
Hi Ram, just a few minor suggestions
|
Update FeatureUtility command-new verify option-2 #6649
Hi Sarah, Incorporated David's Peer Review comments. Could you have a look at David's comments as well as my changes and suggest modifications, if any? Draft links: https://docs-draft-openlibertyio.mqj6zf7jocq.us-south.codeengine.appdomain.cloud/docs/latest/reference/command/featureUtility-installFeature.html Regards, CC @dmuelle |
Hi @ramkumar-k-9286 , I reviewed again after reading David's comment.
| |
Update FeatureUtility command-new verify option-3 #6649
Hi Sarah, Incorporated your review comments. Could you have a look at the changes and see if you are ok with the modifications. Draft links: Regards, CC @dmuelle |
lgtm! |
LGTM, thanks |
Epic moved to 23.0.0.8 |
Hi David @dmuelle Draft links on draft. Regards, |
LGTM, send to staging when you have a chance |
@ramkumar-k-9286 @dmuelle Sorry this is moved to 23.0.0.10. |
Thanks @jjiwooLim - in that case @ramkumar-k-9286 , we can just leave it as is in draft until the feature is ready to release. |
Typo found: --verify = encode should be enforce Specifies how features must be verified. how features should be verified during a process or installation. Supported values are enforce, skip, all, and warn. If this option is not specified, the default value is enforce. enforce: Verifies the signatures of all Liberty features except for user features. It checks the integrity and authenticity of the features that are provided by the Liberty framework. |
FeatureUtility-encode-to-enforce #6649
Hi, @jjiwooLim @dmuelle @lauracowen Corrections done: Corrected one other mistake @lauracowen pointed out: Specifies how features must be verified during a process or an installation. Draft links: Regards, |
I don't see this update in the https://openliberty.io/docs/latest/reference/command/featureUtility-modifications.html |
Hi @jjiwooLim - that information was moved to https://openliberty.io/docs/latest/reference/command/featureUtility-commands.html#_modifications_for_featureutility_commands The link you found was an artifact that needs to be deleted. Apparently the page was removed from the TOC but the file was not deleted. I will delete it in the next doc release to ensure it can't be found by accident. Thanks |
Epic: OpenLiberty/open-liberty#17220
verify
option.enforce
,skip
,all
, andwarn
. If this option isn't specified, a default value ofenforce
is used.-
enforce
: Verifies the signatures of all Liberty features except for user features.-
skip
: Skips verification altogether and does not download any feature signatures.-
all
: Verifies both Liberty features and user features.-
warn
: Same as "all", but it will not terminate installation in the event that verification fails.FEATURE_VERIFY
feature.verify
--verify
option forinstallFeature
andinstallServerFeatures
command.You can verify your user features by providing your public key ID and key URL. Instructions on generating a key pair, signing the user feature and distributing your key can be found here.
The text was updated successfully, but these errors were encountered: