Skip to content
Snippets Groups Projects
  1. Sep 08, 2021
  2. Aug 10, 2021
  3. Aug 06, 2021
  4. Aug 03, 2021
  5. Jul 09, 2021
  6. Jul 01, 2021
    • Kshitij Sobti's avatar
      refactor: Rename CourseEditLTIFieldsEnabledFlag to... · 6fb86793
      Kshitij Sobti authored
      refactor: Rename CourseEditLTIFieldsEnabledFlag to CourseAllowPIISharingInLTIFlag and use it for LTI1.3
      This commit renames the CourseEditLTIFieldsEnabledFlag to CourseAllowPIISharingInLTIFlag since the aim is to expand its scope to all LTI-related PII sharing. It also removes the current LTI1.3 waffle flag for PII sharing.
      6fb86793
  7. Jun 14, 2021
  8. Jun 09, 2021
  9. Jun 05, 2021
  10. Jun 03, 2021
  11. Apr 28, 2021
  12. Apr 21, 2021
  13. Apr 13, 2021
  14. Apr 09, 2021
  15. Mar 22, 2021
  16. Mar 19, 2021
  17. Mar 18, 2021
  18. Mar 03, 2021
  19. Feb 25, 2021
    • stvn's avatar
      fix: Manually backfill lti_config dicts · 7082a991
      stvn authored
      The difficulty here is that the empty string in an invalid JSON
      dictionary (as opposed to None/NULL or '{}' which is just "blank");
      attempts to instantiate models would fail, given the invalid data. This
      meant we couldn't use the Django ORM to handle the migration entirely;
      we need to craft some raw SQL to work-around these checks and
      limitations.
      
      Related-To: 42a9e342
      Related-To: https://github.com/edx/xblock-lti-consumer/pull/144
      7082a991
  20. Feb 24, 2021
    • stvn's avatar
      fix: Manually backfill config_id UUIDs again · 42a9e342
      stvn authored
      The previous backfills handled NULL entries;
      this handles empty strings.
      
      The difficulty here was that since the empty string in an invalid UUID
      (as opposed to None/NULL which is just "blank"), attempts to instantiate
      models would fail, given the invalid data. This meant we couldn't use
      the Django ORM to handle the migration entirely; we need to craft some
      raw SQL to work-around these checks and limitations.
      42a9e342
  21. Feb 23, 2021
  22. Feb 16, 2021
  23. Feb 08, 2021
  24. Feb 04, 2021
    • stvn's avatar
      fix: Migrate the UUID backfill again · 8b17e4a6
      stvn authored
      To correct the, in our case, single database entry that snuck in without
      a UUID during the schema change.
      
      Steps:
      - Make the field editable
      - Add `config_id` to all models missing it
      - Make the field noneditable again
      8b17e4a6
  25. Jan 29, 2021
  26. Jan 25, 2021
  27. Jan 21, 2021
  28. Jan 20, 2021
    • Kshitij Sobti's avatar
      Fix migration `config_id` conflict. · 59b7c431
      Kshitij Sobti authored
      A previous PR (#130) added a new unique field with a default value to the
      LtiConfiguration model. Such cases need special handling in migraiton, however
      the previous PR did not include that. This commit fixes the migration to include
      the special handling for new unique fields.
      59b7c431
  29. Jan 19, 2021
  30. Jan 15, 2021
  31. Dec 17, 2020
    • stvn's avatar
      Skip migration when no LTI XBlock location exists · 9f326ee8
      stvn authored
      otherwise this blows up, trying to migrate a record with no location
      (the modulestore lookup throws).
      
      Presumably this isn't (wasn't?) an issue in prod already, right?
      But I did hit this in my devstack, having previously created an
      LtiConfiguration record via Django Admin (without a location).
      9f326ee8
Loading