[Zuora EoA fields] Remove EoA fields from Zuora local copy

Problem

We no longer need the eoa_starter_bronze_offer_accepted__c field. Let's remove it.

Proposal

This will be a multistep process:

  1. Remove field from Zuora local copy/sync 👈 this issue
  2. [Zuora EoA fields] Exclude fields from Zuora sc... (#12565)
  3. [Zuora EoA fields] Remove fields from Zuora (#12566)
  4. [Zuora EoA fields] Regenerate Zuora schema in Cdot (#12567)

#9729 (comment 2410967088)

This might be the first time remove a field from the Zuora local copy so perhaps we can document the process as we go and add it to this doc. It notes how to add fields but not removing. Using that as a guide to reverse it might be helpful.

  • The ResourceSynchronizer determines the fields to sync using the local resource schema here. So before we remove those fields, we may want to exclude that field temporarily, similar to how we ignore columns in AR.
  • There is also a audit job that checks that resources are in sync that will need to be prepped before we can remove a fields too. Similar to above, we could temporarily exclude that field by adding it to the list here, which would avoid selecting that field in the remote Zuora query. For the local record, the field might need to be excluded here.
  • Tagging @tvellishetty on this as well in case he has any other thoughts on removing a fields from the local copy.

#9729 (comment 2412605989)

@tyleramos Thanks for the great breakdown! I agree on the above steps, I just want to add that when removing the references of eoa_starter_bronze_offer_accepted__c from code, we need to also remove it from the config/zuora/local_copy_backfill_status.yml file.


Next steps (if any)

[Zuora EoA fields] Exclude fields from Zuora sc... (#12565)

Edited by Ryan Cobb