rigmiklos

> We achieved this by using custom config file which has api names by each environment and a Powershell script which runs in a pipeline to filter API's from artifacts...

> We handle environments by using 3 different stages in the run-publisher.yaml that will publish to each different env. It will take a lot of custom code to do what...

> We’ve implemented a per-environment artifacts layout and it works: > > * artifacts-dev/ (Dev snapshot) > * artifacts-test/ (curated subset) > * artifacts-prod/ (curated subset) > > Each stage...

> We’ve implemented a per-environment artifacts layout and it works: > > * artifacts-dev/ (Dev snapshot) > * artifacts-test/ (curated subset) > * artifacts-prod/ (curated subset) > > Each stage...

@megamax34 , sure, looking forward to it > Ill give a more detailed approach of our setup and why we went down the path we did when I have some...

> Maybe we just need a feature in the APIOps override YAML configs to tell the APIOps pipeline to not promote a particular API. This way we can have APIs...

Before closing this issue. From the approaches shared and mentioned, seems like the below are 2 viable approaches. @megamax34 @palmiv @mangeshparanjape would like to brainstorm and get feedback on the...