How to prevent an API operations from being promoted across environments

[umashankar337]

Release version

4.8.0

Question Details

In our API environment, we have split API operations within an product for different releases. Because of this approach, we are testing few API operation for production deployment and parallelly developing some new operations for next releases.

For example:
Product name: Prod1
API name: API1
Operations: POST-A1, POST-A2(First release)
Operations: POST-B1, POST-B2(Second release)

We want to test the operations for first release on pre-prod and deploy them to prod whereas we keep on develop the other operations which are planned for second release.

Expected behavior

There must be a way to choose part of operations those I want to keep for the deployment to other downstream environments.

Actual behavior

I am not sure if that is possible.

Reproduction Steps

You can use question section to find the reproduction steps.

[github-actions]

  Thank you for opening this issue! Please be patient while we will look into it and get back to you as this is an open source project. In the meantime make sure you take a look at the [closed issues](https://github.com/Azure/apiops/issues?q=is%3Aissue+is%3Aclosed) in case your question has already been answered. Don't forget to provide any additional information if needed (e.g. scrubbed logs, detailed feature requests,etc.).
  Whenever it's feasible, please don't hesitate to send a Pull Request (PR) our way. We'd greatly appreciate it, and we'll gladly assess and incorporate your changes.

[guythetechie]

It's not possible with ApiOps. Your operations all get bundled into one specification file, and you can't select which make it there.

I would look into revisions, which is APIM's way of handling what you're trying to accomplish.

[guythetechie]

Note that revisions are currently bugged (#436) in ApiOps. Should be fixed in our next major release.

[umashankar337]

Thanks for your feedbacks.