Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] How to override Cors policy in QA and prod env #454

Closed
JashwanthGuvvala opened this issue Jan 8, 2024 · 2 comments
Closed

[BUG] How to override Cors policy in QA and prod env #454

JashwanthGuvvala opened this issue Jan 8, 2024 · 2 comments

Comments

@JashwanthGuvvala
Copy link

Release version

v5.0.1

Describe the bug

How to override API's Cors policy in QA and prod env

Expected behavior

How to override API's Cors policy in QA and prod env

Actual behavior

How to override API's Cors policy in QA and prod env

Reproduction Steps

How to override API's Cors policy in QA and prod env

Copy link

github-actions bot commented Jan 8, 2024

  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.

@waelkdouh
Copy link
Contributor

Your best bet is to use namedvalues within your policy and override them across environments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants