When exporting APIs, operations need to be in a consistent order (from APIOps Toolkit customer)

[petehauge]

Description

We heard from an existing APIOps Toolkit customer that they were seeing issues with exporting APIs, where the operations were in an inconsistent order. This caused issues with clean source code diffs, they had difficulty seeing through the noise to see the real changes. We should:

• Ensure that this isn't an issue with apiops-cli
• Write a few unit tests to ensure it doesn't regress

[EMaher]

@petehauge Given how the cli executes things in parallel, I'm not sure this is possible. I believe the original issue was that customer wanted to be able to easily be able to tell if anything had changed in the api surface and take an action based on that information. What do you think about expanding the compare operator to solve that issue. Something like
apiops compare local --source --commit-id
which would compare the files in the source directory, assuming they are under a github repository, from the specified commit to the current files (even if not committed)

(local is the sub command that says look at extracted files, not the azure resource).

[petehauge]

@EMaher So far we've seen that users want to use their existing source code tools for this (diff, pull request, etc) so I think we should focus on making that the best experience. Let's talk about this one directly on what might be possible!