Specify method configuration version as part of job submission
Suppose I have some automation that calls the createSubmission API endpoint and I intend this automation to use the same method and configuration every time, because it's a production workflow running in a production workspace. The problem is that this endpoint requires a methodConfigurationName but not a method config version. Instead, it seem to use the method config with the highest version number.
Now, suppose someone makes a one-off modification to the method config via the Terra UI or the Firecloud API, creating a new method config version in this workspace. The next time my automation runs, it'll choose the modified method config instead of the one I consider to be the locked-down production version.
I don't know of way to ensure the config is correct other than re-registering the production method config before I create a new submission. This will obviously create a huge number of versions over time, though.
My strong preference would be for the createSubmission endpoint to just let me supply the inputs/outputs/etc. directly instead of requiring a method config at all, but at the very least it would be nice if the endpoint let me specify a version number.
Comments
1 comment
This totally makes sense to me as well.
We had to invent cumbersome workarounds for this, especially when people are collaborating in a busy workspace.
Beth Sheets Adam Mullen Adam Nichols please let us know if we can help with anything.
Please sign in to leave a comment.