Repository navigation
[FEATURE REQ] Support renaming named values #837
Description
Activity
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.Konrad Windszus (@kwin) - I'll add this to our list to investigate. Note that this is an APIM limitation: the portal won't let you create a named value with an already existing display name.
Can you tell me more about your use case? Are you running the publisher with a commit where the named value has been renamed? Or is this a publish all scenario (no commit id)?
This is initial publish all after previously manually maintaining the config. The different environments had different names with same display names which leads to errors during publishing.
Please describe the feature.
If a named value with the same
displayNamebut a differentnamedoes already exist in APIM while publishing the following error is emittedCurrently this requires manual deletion of the existing named value before publishing succeeds. Would be nice to automatically such cases within the publisher client.