fix: exporter sanitizing content to delete

[alex-sheehan-edx]

Merge checklist:

• Any new requirements are in the right place (do not manually modify the requirements/*.txt files)
  • base.in if needed in production but edx-platform doesn't install it
  • test-master.in if edx-platform pins it, with a matching version
  • make upgrade && make requirements have been run to regenerate requirements
• make static has been run to update webpack bundling if any static content was updated
• ./manage.py makemigrations has been run
  • Checkout the Database Migration Confluence page for helpful tips on creating migrations.
  • Note: This must be run if you modified any models.
    • It may or may not make a migration depending on exactly what you modified, but it should still be run.
  • This should be run from either a venv with all the lms/edx-enterprise requirements installed or if you checked out edx-enterprise into the src directory used by lms, you can run this command through an lms shell.
    • It would be ./manage.py lms makemigrations in the shell.
• Version bumped
• Changelog record added
• Translations updated (see docs/internationalization.rst but also this isn't blocking for merge atm)

Post merge:

• Tag pushed and a new version released
  • Note: Assets will be added automatically. You just need to provide a tag (should match your version number) and title and description.
• After versioned build finishes in GitHub Actions, verify version has been pushed to PyPI
  • Each step in the release build has a condition flag that checks if the rest of the steps are done and if so will deploy to PyPi.
    (so basically once your build finishes, after maybe a minute you should see the new version in PyPi automatically (on refresh))
• PR created in edx-platform to upgrade dependencies (including edx-enterprise)
  • This must be done after the version is visible in PyPi as make upgrade in edx-platform will look for the latest version in PyPi.
  • Note: the edx-enterprise constraint in edx-platform must also be bumped to the latest version in PyPi.

[katrinan029]

LGTM! Thank you for walking through these changes with me.

[johnnagro]

the approach looks good. i would recommend a few tweaks. i'd love to know if we can factor out that need to hold back on the content_last_modified timestamp.

[katrinan029]

quick question: In what instance will this be used? Where is this attribute defined?

[alex-sheehan-edx]

The intention's to go into the channel specific content metadata exporter and use the defined mappings to tailor and sanitize the code (see https://github.com/openedx/edx-enterprise/blob/master/integrated_channels/sap_success_factors/exporters/content_metadata.py). There we have two different types of mapping methods, transform_{attribute} and transform_{content_type}_{attribute} because some external platforms care about and want to distinguish between metadata depending on what type of content it is, ie SAP wants different titles for course runs than for course and programs. In this case we're supporting the old implementation while also allowing for the caller to specify more detail/actions. transform_{content_type}_{attribute} isn't currently being used by any channel yet but I wanted to add the functionality as we know channels do this content specific mapping already and we may want to support it in an upgrade in the future.

[johnnagro]

🥇