Skip to content

Conversation

@sameenfatima78
Copy link
Member

@sameenfatima78 sameenfatima78 commented Nov 19, 2025

As part of the initiative to make integrated_channels a separately installable plugin: https://github.com/openedx/enterprise-integrated-channels, we are temporarily making use of a feature flag to point to new data models. Once the changes are tested, we will roll out a change in openedx to remove the feature flag and entirely rely on new models that live within the channel_integrations app.

@sameenfatima78 sameenfatima78 requested a review from a team as a code owner November 19, 2025 12:03
setup_retirement_states
)

# This is a temporary import path while we transition from integrated_channels to channel_integrations
Copy link
Member

Choose a reason for hiding this comment

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

could you add a timeline or link to a publicly available ticket to this comment?

Copy link
Member Author

Choose a reason for hiding this comment

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

We don't have a publicly available ticket but this will be done as soon as we can test the changes on edx/edx-platform repo and confirm everything is working.

Copy link
Member

Choose a reason for hiding this comment

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

Could you add this to the core settings file opened/envs/common.py and add a full toggle annotation? By keeping all of our settings in the central envs/ files, it helps us keep track of them and document them. And as Deborah mentioned pleased create an edx-platform GitHub issue and include a link to it in the .. toggle_tickets. You can declare the default as True there.

Furthermore, please access the setting directly (settings.ENABLE_LEGACY_INTEGRATED_CHANNELS) in all places instead of using getattr. This way, we will get a helpful exception if the setting name is misspelled or if any setting references are accidentally left behind once the definition is removed.

from .signals import USER_RETIRE_LMS_CRITICAL, USER_RETIRE_LMS_MISC, USER_RETIRE_MAILINGS
from .utils import create_retirement_request_and_deactivate_account, username_suffix_generator

# This is a temporary import path while we transition from integrated_channels to channel_integrations
Copy link
Member

Choose a reason for hiding this comment

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

same comment as above.

Copy link
Member Author

Choose a reason for hiding this comment

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

same reply as above.


from ...models import UserOrgTag

# This is a temporary import path while we transition from integrated_channels to channel_integrations
Copy link
Member

Choose a reason for hiding this comment

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

same

from openedx.features.enterprise_support.tasks import clear_enterprise_customer_data_consent_share_cache
from openedx.features.enterprise_support.utils import clear_data_consent_share_cache, is_enterprise_learner

# This is a temporary import path while we transition from integrated_channels to channel_integrations
Copy link
Member

Choose a reason for hiding this comment

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

same

Copy link
Member

@deborahgu deborahgu left a comment

Choose a reason for hiding this comment

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

wait, it looks like the feature flag isn't configured for edx platform. are you planning on doing that?

@deborahgu
Copy link
Member

another question: is there a formal DEPR for removing the old code from edx-platform? It's probably a fast track since you're doing a drop-in replacement, but since it will be a breaking change for people who don't implement the plug-in, it's possible it also needs to go through that process.

@sameenfatima78
Copy link
Member Author

wait, it looks like the feature flag isn't configured for edx platform. are you planning on doing that?

@deborahgu Feature flag is defined here for edx-platform: https://github.com/edx/edx-internal/pull/13511
The default value is set to True so for openedx/edx-platform instance will continue to use legacy integrated_channels functionality. For the forked repo edx/edx-platform, the value is already set to False on production and stage.

@sameenfatima78
Copy link
Member Author

another question: is there a formal DEPR for removing the old code from edx-platform? It's probably a fast track since you're doing a drop-in replacement, but since it will be a breaking change for people who don't implement the plug-in, it's possible it also needs to go through that process.

@deborahgu Could you guide me on what that process looks like? Also, since we are short on time and need to provide urgent support to a customer by merging this fix, would you recommend merging these changes into the forked repository for now?

fix: fixed tests and quality failures
setup_retirement_states
)

# This is a temporary import path while we transition from integrated_channels to channel_integrations
Copy link
Member

Choose a reason for hiding this comment

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

Could you add this to the core settings file opened/envs/common.py and add a full toggle annotation? By keeping all of our settings in the central envs/ files, it helps us keep track of them and document them. And as Deborah mentioned pleased create an edx-platform GitHub issue and include a link to it in the .. toggle_tickets. You can declare the default as True there.

Furthermore, please access the setting directly (settings.ENABLE_LEGACY_INTEGRATED_CHANNELS) in all places instead of using getattr. This way, we will get a helpful exception if the setting name is misspelled or if any setting references are accidentally left behind once the definition is removed.

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.

4 participants