Use case:

• we have a few entries in the catalog that have an incorrect "External ID" value.
• a number of incidents and other catalog entries are referring to these erroneous entries
• we want to fix external IDs, but it is not possible without recreation of entry
• I've updated the source file to use proper external IDs
• I want to run sync command now, but it will try to remove erroneous entries, according to --dry-run output.
• I'm not sure how incident.io will behave and if the importer will be able to remove entries that are referred in incidents (custom fields)
• We don't want to lose this incident meta data, so I want to:
  • create new "correct" entries
  • update all custom field values to point to "correct" entry using external ID value (we don't want to use aliases, it will make things complicated)
  • remove old "erroneous" entries

It would be nice to have a CLI option like --no-prune-missing-entries. If true, do not remove entries that are present in catalog but missing from source file.

Related flags that didn't help me:

• --no-prune works only for types
• --no-allow-delete-all works only when all entries are missing from source file