-
Notifications
You must be signed in to change notification settings - Fork 202
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] Allow overriding of API diagnostics in v6 #672
Comments
|
@tomsauret21 - can you post your sample configuration file with the override and the error message? |
Here is a sample from our configuration file
Here is the error we are receiving If we roll back to v5 of the publisher, the API will deploy without errors. But when using v6 it will fail for every API that has a "Diagnostics" folder included with it. |
Thank you. We'll get this fixed. |
Release version
v6.0.1.1
Describe the bug
When deploying APIs that have diagnostic settings included, you will get an error that the extracted diagnostic setting does not exist. It is not overriding the value with what is specified in the configuration file. If we roll back to v5 it will deploy without error
Expected behavior
Be able to deploy APIs with diagnostic settings with the latest version
Actual behavior
Deployments are failing with errors pointing to the logger Id not being updated with the value from the configuration file for that environment.
Reproduction Steps
Extract api
ensure it has the Diagnostics folder included in the repository
deploy using v6 of the publisher
The text was updated successfully, but these errors were encountered: