Project_O "o" command used from an instance principal

Can the "o" command be used from an instance principal defined in a dynamic group similarly to how regular oci commands can be used? I noticed "o" works from a cloud shell host so I was hoping it worked equally well from instance principal hosts to perform selected tasks from them.

When I ran "o oci_commands" it seemed to be working but the resulting oci_commands file just has a header followed by a bunch of blank lines in it. I ran "export OCI_CLI_AUTH=instance_principal" and retried but got the same result.

Update: Copying the ocids and oci_commands from my Dev laptop to the host's ~/.oci directory seems to be working correctly w/o need for a config file I just had to set OCI_CLI_AUTH as above. Thinking it may be a viable workaround. Please let me know if there's a better way or if some changes to o's code may be needed to fully support its use from an instance principal.

"o" is a great wrapper for working with the underlying OCI commands. It makes scripting and ad hoc tasks much easier and a lot more concise. Love it!

Thanks,
Jim

Start by reproducing o oci_commands on an instance-principal host with OCI_CLI_AUTH=instance_principal, comparing it with the copied ~/.oci/ocids and ~/.oci/oci_commands workaround described in the issue. Trace the o command's generation path and verify that the completed output contains usable OCI commands rather than a header and blank lines.