Region inconsistency in OCIDs

There is an inconsistency in the way OCIDs are allocated among resources from region to region. For example:

• Ashburn compute instance: ocid1.instance.oc1.iad.........
• Frankfurt compute instance: ocid1.instance.oc1.eu-frankfurt-1....
  In my opinion this should be either iad, fra .... or us-ashburn-1, eu-frankfurt-1 for consistency reasons.

Anyway, both types of region quelifiers appear in the documentation and can be used in CLI commands.

The bigger problem is for Storage resources which in Frankfurt for example no longer contain eu-frankfurt-1, but eu_frankfurt_1, for example:

• ocid1.filesystem.oc1.eu_frankfurt_1...
• ocid1.mounttarget.oc1.eu_frankfurt_1...

This is annoying while working for example on a tagging script that takes an OCID of a resource and extracts from it the type of resource, the region and uses them for updates. You cannot make an update on region eu_frankfurt_1, because CLI only knows about fra and eu-frankfurt-1.

Start by reproducing the reported OCID region values for Ashburn and Frankfurt compute and Storage resources, then compare them with the region qualifiers accepted by OCI CLI commands. Trace where the CLI parses or validates OCID regions; done means the inconsistent eu_frankfurt_1, eu-frankfurt-1, and abbreviated forms are handled consistently for the affected resources.