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

[Question] Imported API from AzureFucntion APP. different Environments have different backend which created different backend named values #546

Closed
eamitshaw opened this issue May 9, 2024 · 2 comments

Comments

@eamitshaw
Copy link

Release version

APIOPs V 5.1.1.

Question Details

We have imported APIs from azure functions. Different environments have different backend azure function name. So it created a different named values/Backend names in APIM of different environments. How could we use the extracted yaml to publish correct names/reference for promoted environments.
Note- we do not have any option to give the named value for azure function key any custom name. it is being created automatically by APIM.

Expected behavior

Publisher could have an option to replace the name for named values/backend name with promoted environment .

Actual behavior

Publisher searches for matching names for named value name/backend names.

Reproduction Steps

Create two different azure function apps with different names for different environments.
Create two APIMs for each environment and import apis from previously created azure functions.
it will create named values and backends and there are no option to change those names during creations.

Now try to run the pipeline and check if the named value/backend

Copy link

github-actions bot commented May 9, 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.

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

1 participant