feat: Add config-manager push iga-workflows command

[dallinjsevy]

I added a function to push iga workflow configurations for the frodo config-manager push iga workflows command.

I also added the command implementation file to enable the command.

[vscheuber]

@dallinjsevy can you take a look at the failing tests? I rebased the PR but lots of snapshots are still failing (at least in the pipeline).

[dallinjsevy]

@vscheuber Yeah, I'll take a look at those this morning and push the fix.

[phalestrivir]

@vscheuber I'm trying to look into it. It looks like it's expecting the snapshot to contain that there's a new frodo version. I just had it reproduced on my local machine, although after I ran a build again (without changing anything) it stopped showing up, so not sure what happened. I'm going to see if I can find a consistent way to reproduce it, but I'm guessing it has to do with how it's getting built in the pipeline

[phalestrivir]

@vscheuber It looks like the issue is that it is building the binary with version 2.0.0-trivir.2. I have no idea where that's coming from. My understanding is that it should be pulling from the package.json, which has version 4.5.4, but it doesn't seem to be doing that. I'll keep looking into the pipeline.yml to see if there might be a way to fix it to pull the right version

[vscheuber]

@phalestrivir yes, I saw that, too, and couldn't really explain it. Let me checkout the PR and run the tests locally. If they succeed, then I'll merge the PR at risk and expect the tests to succeed once everything is in main.

[phalestrivir]

@phalestrivir yes, I saw that, too, and couldn't really explain it. Let me checkout the PR and run the tests locally. If they succeed, then I'll merge the PR at risk and expect the tests to succeed once everything is in main.

Ok, let me remove my commit real quick, I was just using it to print out the versions to see why it was failing. I feel like there is an issue with the pipeline not building with the right version, but I'm not familiar enough with it yet to know how it fix it.

[vscheuber]

@phalestrivir that worked. I think it's getting the version from your repo somewhere. And since the tests really straddle envs between rockcarver and trivir, somehow your version must have slipped into this PR. I don't recall this ever happening with any other of your PRs. But I checked out the PR, ran the tests locally and they succeeded, so I merged at risk and the release just popped out.

[phalestrivir]

@phalestrivir that worked. I think it's getting the version from your repo somewhere. And since the tests really straddle envs between rockcarver and trivir, somehow your version must have slipped into this PR. I don't recall this ever happening with any other of your PRs. But I checked out the PR, ran the tests locally and they succeeded, so I merged at risk and the release just popped out.

That's very interesting. Yeah, I have no idea how that slipped in with the PR. My only guess would be that the branch may have initially been created off of our trivir branch in our repo and then was later rebased with the main branch (which we keep synced with the Rockcarver main branch), but usually we try to branch off of main so we don't have to do that. Either way, I'm glad it worked out.