-
Notifications
You must be signed in to change notification settings - Fork 604
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
Versionless support for featureUtility #28165
Labels
Comments
cbridgha
added
Versionless Beta
Issues relating to versionless features beta
versionless support
Associated issue with the versionless feature support #25704
in:Install
Versionless
and removed
Versionless Beta
Issues relating to versionless features beta
versionless support
Associated issue with the versionless feature support #25704
labels
Apr 16, 2024
Part of #25704 |
This was referenced Apr 16, 2024
This was referenced May 1, 2024
Merged PR's for this issue:
|
github-project-automation
bot
moved this to Completed Versionless Tasks
in Versionless Features Development
Aug 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Changes to featureUtility resolution and overall support for versionless features.
The following command is required to be supported
featureUtility installServerFeatures <server name>
installServerFeatures knows the complete set of features being used, and uses the normal kernel resolution code to work out what features to install.
The list of features returned by installServerFeatures, should be a "resolved" list of "versioned" features, and "should" not require any special handling for "version-less" features. But needs to be tested
We are NOT supporting:
$ ./featureUtility installFeature <versionless feature>.
Other than an error message should appearCurrently - if a versionless feature exists in the repo it shows this message:
$ ./featureUtility installFeature mpHealth --verify=all
CWWKF1250I: The following assets already exist: [mpHealth]. They will not be reinstalled. To modify an existing feature, you must manually uninstall it first.
This needs to change to always fail for versionless... like what we show for a feature not found or possibly a new message...
$ ./featureUtility installFeature mpConfig --verify=all
Initializing ...
Using 8 threads to download artifacts.
CWWKF1409E: Unable to find the following feature
The text was updated successfully, but these errors were encountered: