Azure / apiops

APIOps applies the concepts of GitOps and DevOps to API deployment. By using practices from these two methodologies, APIOps can enable everyone involved in the lifecycle of API design, development, and deployment with self-service and automated tools to ensure the quality of the specifications and APIs that they’re building.
https://azure.github.io/apiops
MIT License
328 stars 193 forks source link

[Question] How to override gateways in configuration.yaml file? #680

Closed karthikpeddi115 closed 1 month ago

karthikpeddi115 commented 1 month ago

Release version

v6.0.1.1

Question Details

Gone through wiki, it doesn't have exact way to override gateway names in higher environments, please help with one example.

Expected behavior

Gone through wiki, it doesn't have exact way to override gateway names in higher environments, please help with one example.

Actual behavior

Gone through wiki, it doesn't have exact way to override gateway names in higher environments, please help with one example.

Reproduction Steps

Gone through wiki, it doesn't have exact way to override gateway names in higher environments, please help with one example.

github-actions[bot] commented 1 month ago
  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 commented 1 month ago

@karthikpeddi115 - you cannot override names with ApiOps. You can only override properties.

If you have gatewayA in dev, you cannot rename it to gatewayB in prod. The names have to be consistent.