Upsert on re-syncing w/ cli

[TheHumanJenkins]

There is some unintentional behavior with the CLI allowing the creation/update on an oas re-sync. I would think if you pass an incorrect OAS ID on an update or re-sync it would result in an error.

I am able to pass a categoryID to this cli and it will create a new OAS definition; hence duplicating the spec within a project.

Unless the method is designed to be an upsert; but the documentation isn’t clear that if you pass an id that doesn’t exists it will create the oas using that id. Probably this is an unintentional design or docs are incorrect.

Docs:
This will edit (re-sync) an existing API definition (identified by --id) within your ReadMe project. This is the recommended approach for usage in CI environments.

rdme openapi [url-or-local-path-to-file] --id={existing-id}

[kanadgupta]

Thanks for flagging this @TheHumanJenkins! You've discovered some legacy behavior that was added in support of our previous GitHub Action (that has been sunset for well over a year now and hasn't been usable in the GitHub Actions runners since a few months ago). This upsert behavior is undocumented and we don't recommend utilizing it since it's in our backlog to remove this logic entirely.