Preserve integration info during course clone

[elenabaurkot]

Add opt-in settings to copy integration_id and integration_data on assignments during course copy. External systems rely on these fields to correlate Canvas assignments with third-party records and assignments across courses can share the same IDs.

We reuse intergration_ids and integration_data across courses to be able to track assignment data between courses and semesters. I opened a support ticket and was told integration_data should copy over and that integration_ids were meant to be unique, but since these link to third parties was hopeful people could opt into maintaining over course clone in case the same courses need to link to the same third party data for our case.

Our data team uses DAP (data access platform) to access Canvas data and it only contains integration_id for assignments not integration_data. If we are able to clone only integration_data on course clone, could this potentially be added to DAP?

Test Plan:

• Create a course with assignments that have integration_id and integration_data set
• Copy the course with both options enabled
• Verify cloned assignments retain the values
• Copy again with options disabled
• Verify fields are cleared (default behavior)
• Test via API: POST course copy with settings[copy_integration_ids]=true
• Verify same behavior as UI

[viszpis]

👋 One more thing, I think this feature needs to be behind a Feature Flag. The flag should be defined in config/feature_flags/00_standard.yml Something like this

course_copy_allow_copying_integration_info:
  applies_to: SiteAdmin
  state: hidden
  display_name: Course Copy: allow copying integration_id and integration_data
  description: Adds opt-in settings to copy integration_id and integration_data on assignments during course copy
  environments:
    ci:
      state: allowed_on
    development:
      state: allowed_on

This should control the import/export flow plus the UI rendering (the checkbox rendering) part.

[elenabaurkot]

Thanks for the feedback @viszpis, I've updated the PR with the combined setting, feature flag and environments block. Quick question: once this merges, what's the typical process for enabling a SiteAdmin flag in production? We'd love to be able to use this feature on our instance.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[spencerolson]

Hi @elenabaurkot this generally looks good, but currently the test suite is failing. Two of the tests you added have failing assertions. Can you fix those please? Thanks!

[spencerolson]

this assertion is failing with:

Failure/Error: expect(a_to.integration_data).to be_nil

 expected: nil
      got: {}

[spencerolson]

this assertion is failing with:

Failure/Error: expect(a1_to.integration_data).to be_nil

 expected: nil
      got: {}