Summary of request
The kf profile introduced a small list of alternate classes that are only used for the KF Client/Server. Score will no longer directly support kf so this profile is being removed. Consequently, we want to remove all the alternate classes that are only used with the kf profile.
This will additionally let us remove all references to the kf profile throughout the code base.
Details
Additional Context
All references to this profile live in the Score Client. I believe this is a consequence of integrating the Score CLI with a custom backend (not Score Server) during the KF project. These projects are therefore disconnected and this integration can't be maintained within the main Score repo. If the current state needs to be persisted, it should be forked from Score version 5.11.0
Summary of request
The
kfprofile introduced a small list of alternate classes that are only used for the KF Client/Server. Score will no longer directly supportkfso this profile is being removed. Consequently, we want to remove all the alternate classes that are only used with thekfprofile.This will additionally let us remove all references to the
kfprofile throughout the code base.Details
metadata/kfdirectory"!kf"Profile annotation fromLegacyMetadataServicescore/score-client/src/main/java/bio/overture/score/client/metadata/legacy/LegacyMetadataService.java
Lines 31 to 32 in f931ebe
"!kf"from CLI Commandsscore/score-client/src/main/java/bio/overture/score/client/command/MountCommand.java
Lines 70 to 71 in f931ebe
score/score-client/src/main/java/bio/overture/score/client/command/UploadCommand.java
Lines 47 to 48 in f931ebe
score/score-client/src/main/java/bio/overture/score/client/command/ViewCommand.java
Lines 68 to 69 in f931ebe
kfconfig from the application.ymlkfandkfportalproperties in common profile:score/score-client/src/main/resources/application.yml
Lines 39 to 48 in f931ebe
kfactive profile configscore/score-client/src/main/resources/application.yml
Lines 85 to 103 in f931ebe
kfconfig from the test application.ymlAdditional Context
All references to this profile live in the Score Client. I believe this is a consequence of integrating the Score CLI with a custom backend (not Score Server) during the KF project. These projects are therefore disconnected and this integration can't be maintained within the main Score repo. If the current state needs to be persisted, it should be forked from Score version 5.11.0