Skip to content
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

SAK-50378 LTI - Remove Tool Features / Rationalize DB Fields #12844

Closed
wants to merge 8 commits into from

Conversation

csev
Copy link
Contributor

@csev csev commented Sep 3, 2024

This need to land after Zhuo's JIRA 50427 lands. I will rebase this once his code is in master. But folks can look at it now.

@csev csev marked this pull request as draft September 3, 2024 14:52
@csev
Copy link
Contributor Author

csev commented Sep 5, 2024

This will need a rebase once #12851 is in master - so I have it draft for now.

Comment on lines +2 to +33
-- These are columns dropped by SAK-50378 but will not be droppped by
-- the Sakai 25 conversion scripts until Sakai 25.2 or later
-- New Sakai 25 instances won't have these columns but the columns will
-- not be removed as systems go from Sakai 23 to Sakai 25.0 or 25.1 to allow
-- for forward and backward version movement for early versions of Sakai 25

ALTER TABLE lti_tools DROP COLUMN

ALTER TABLE lti_content DROP COLUMN pagetitle;
ALTER TABLE lti_content DROP COLUMN toolorder;
ALTER TABLE lti_content DROP COLUMN consumerkey;
ALTER TABLE lti_content DROP COLUMN secret;
ALTER TABLE lti_content DROP COLUMN settings_ext;
ALTER TABLE lti_content DROP COLUMN fa_icon;

ALTER TABLE lti_tools DROP COLUMN allowtitle;
ALTER TABLE lti_tools DROP COLUMN pagetitle;
ALTER TABLE lti_tools DROP COLUMN allowpagetitle;
ALTER TABLE lti_tools DROP COLUMN allowlaunch;
ALTER TABLE lti_tools DROP COLUMN allowframeheight;
ALTER TABLE lti_tools DROP COLUMN allowfa_icon;
ALTER TABLE lti_tools DROP COLUMN toolorder;
ALTER TABLE lti_tools DROP COLUMN allowsettings_ext;
ALTER TABLE lti_tools DROP COLUMN allowconsumerkey;
ALTER TABLE lti_tools DROP COLUMN allowsecret;

-- Also while not a database conversion per se, there is an undocumented property that causes
-- The LTI service to derive or fake most of these values when tools are retrieved from the DB
-- post Sakai 25. This is defaulted to "false" for testing and hopefuly it will not be needed
-- and can be deleted at Sakai 25.2 or later

sakai-sak-50328-fake-deprecated-values=true
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would remove this txt file and PR to sakai-reference

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also lets not talk about versions when things happen because in my experience they just end up changing.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK

Comment on lines +179 to +182
// SAK-50378 - If requested (i.e. we found something wrong after Sakai-25 is released), we fake up deprecated values
// This is quicker than a patch and can be used while a patch is being developed and/or for
// testing to see if the deleted columns caused a regression
// This entire block of code can be removed after Sakai 25.2 if it is not needed by then
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lets not discuss Sakai versions in code

// This is quicker than a patch and can be used while a patch is being developed and/or for
// testing to see if the deleted columns caused a regression
// This entire block of code can be removed after Sakai 25.2 if it is not needed by then
String ltiFakeDeprecated = serverConfigurationService.getString("sakai-sak-50328-fake-deprecated-values", "false");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe we can talk about this?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure - I will leave it in and we can review at the Tuesday meeting. I will fix the indentation tho :)

csev and others added 5 commits September 5, 2024 13:49
…Foorm.java

Co-authored-by: Earle Nietzel <earle@longsight.com>
…Foorm.java

Co-authored-by: Earle Nietzel <earle@longsight.com>
…Foorm.java

Co-authored-by: Earle Nietzel <earle@longsight.com>
…LTIService.java

Co-authored-by: Earle Nietzel <earle@longsight.com>
…Foorm.java

Co-authored-by: Earle Nietzel <earle@longsight.com>
@csev csev changed the title LTI - Remove Tool Features / Rationalize DB Fields SAK-50378 LTI - Remove Tool Features / Rationalize DB Fields Sep 5, 2024
@csev csev closed this Sep 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants