Please build and deploy using blow content-editor and content-plugin tags for above bug fix.
Content Editor:
Tag: release-5.2.1_RC4
Content Plugins:
Tag: release-5.2.1_RC4
Hot-fix 5.7.0 (14-02-2024)
Bugs:
Portal: When content creator TN tried to save course, its throwing error "Something went wrong" -KN-973
[Mobile][SSO]: After accepting the Global Consent pop up, the user navigates to the 'Edit Profile' screen, where the user is unable to select the fields. - KN-974
We can utilize the Flink job created by the inquiry team to update user PII data in Knowlg, along with the necessary configuration changes. The details are provided below for your reference:
Variables Added For user-pii-data-updater Flink job:
Variable Name
Description
Default Value
user_pii_updater_kafka_topic_name
Input Kafka Topic Name
{{ env_name }}.delete.user
user_pii_updater_group
Group Name For The Flink Job
{{ env_name }}-user-pii-updater-group
user_pii_target_object_types
Target Object Type and Schema Version should be configured as value .
e.g: If you want to process 5 different objects for deleted user, then all 5 object types should be part of this configuration along with corresponding schema versions.
'{ "Content": ["1.0"], "Collection": ["1.0"] }'
user_pii_replacement_value
The value which need to be inserted for target pii fields.
"Deleted User"
admin_email_notification_enable
This falg is used to enable/disable email notification for admin
true
user_org_service_base_url
Base Url of userorg service for sending notification
"http://{{private_ingressgateway_ip}}/userorg"
email_notification_subject
Subject Line for Email Notification
"User Account Deletion Notification"
email_notification_regards
Value For Regards in Email Notification
"Team"
NOTE: If any adopter is deploying Knowlg alone, they should extract this specific job from the inQuiry codebase and include the mentioned configurations. Alternatively, if they are using both Knowlg and inQuiry, they only need to update the configuration values for user_pii_target_object_types that encompass both Knowlg and inQuiry objects.
Configuration/Environment variable changes:
In this release, we have deprecated the Sunbird Learning service, including an API that was previously served by this service. We have relocated this API to the Sunbird content service. Consequently, we need to update the Kong file to ensure that the upstream URL for the license validation API (asset/v3/validate) points to the Content service instead of the Learning service.
Breaking changes (The existing features will break the if we don’t do the below actions):
During the upgrade to version 5.7.0, it is essential to ensure that the mentioned services and environments are properly updated. Previously, the APIs mentioned were part of the sunbird-learning-service, but now they have been moved to the content-service without altering the API contract. Additionally, changes have been made to ensure that these APIs are no longer served from the sunbird-learning-service.
Therefore, it is crucial to verify that the necessary updates are implemented correctly for a smooth transition to version 5.7.0.
