You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the "supporting independent teams" chatper in the documentation it's stated that "We envision having an operators team who will be responsible for APIM instance configurations (name/values, diagnostics settings, global policies, etc.) as well as different teams who will be exclusively focused on developing a subset of artifacts (e.g. separate apis or products)." but all the extraction includes the policy.xml of the "all apis" policies.
I don't know if this was made on purpose but in this way, we may easly have different extraction with incoherent policy.xml and the hypotetical "operators team" wuold not be the only responsible for that part.
I my opinion, there should be a way to configure (in the extractor configuration file) whenever extracting the global policies or not.
Ciao,
Andrea
The text was updated successfully, but these errors were encountered:
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.
For now we don't support excluding any global artifacts. In the future we envision the newly announced Azure APIM workspaces feature to take care of these specific use cases. For now you can use the gitignore file to exclude any artifacts within your repository.
Please describe the feature.
Hi,
In the "supporting independent teams" chatper in the documentation it's stated that "We envision having an operators team who will be responsible for APIM instance configurations (name/values, diagnostics settings, global policies, etc.) as well as different teams who will be exclusively focused on developing a subset of artifacts (e.g. separate apis or products)." but all the extraction includes the policy.xml of the "all apis" policies.
I don't know if this was made on purpose but in this way, we may easly have different extraction with incoherent policy.xml and the hypotetical "operators team" wuold not be the only responsible for that part.
I my opinion, there should be a way to configure (in the extractor configuration file) whenever extracting the global policies or not.
Ciao,
Andrea
The text was updated successfully, but these errors were encountered: