When we are migrating applications including data, if there are changes in operator instances and if the operator records are associated to any of the application rulesets, then they will also get packaged and migrated to higher environments.
Operators records should be considered as environment specific configuration and it would be a security risk to copy operator records from one environment to another, and we strongly recommend not to package operators as part of deployments.
Here are somethings to consider if the operators records do end up as part of package for deployment.
The operator records will be disabled by default and need to be updated manually after deployment.
If the operators are marked as aged updates,, selecting the “overwrite” option will deploy the operator as enabled along with the password.
If you are deploying operators along with package and got aged updates on operator instances, make sure before you click on “overwrite” option because it deploys the operator as enabled along with the password.