In Data Pipelines, Schedules should not be part of the definition

[schneiw]

The request is to ensure Schedules are not included in the definition of a Data Pipeline for purposes of Deployment Pipelines.

Today, when we deploy content across environments, the item frequently appears as “different” because the schedule configuration is included in the comparison. This creates constant noise and makes it harder to identify meaningful differences.

More importantly, a schedule configured in DEV or TEST can be promoted into PROD as part of a deployment. This creates a real operational risk and is unacceptable — PROD scheduling must be managed independently and explicitly, not carried over from lower environments.