Baoyuantop opened a new pull request, #12411:
URL: https://github.com/apache/apisix/pull/12411

   ### Description
   
   We changed the attribute of the Opentelemetry plugin to metadata in PR 
https://github.com/apache/apisix/pull/11940. After that, users can set the 
`set_ngx_var` property in metadata. However, the generated template file still 
relies on the `set_ngx_var` property from the plugin attribute to predefine 
variables 
https://github.com/apache/apisix/blob/master/apisix/cli/ops.lua#L553-L556, 
which will confuse users. This PR removes this judgment and allows this 
property to be controlled in metadata only.
   
   #### Which issue(s) this PR fixes:
   <!--
   *Automatically closes linked issue when PR is merged.
   Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
   -->
   Fixes #12402
   
   ### Checklist
   
   - [x] I have explained the need for this PR and the problem it solves
   - [x] I have explained the changes or the new features added to this PR
   - [ ] I have added tests corresponding to this change
   - [ ] I have updated the documentation to reflect this change
   - [ ] I have verified that this change is backward compatible (If not, 
please discuss on the [APISIX mailing 
list](https://github.com/apache/apisix/tree/master#community) first)
   
   <!--
   
   Note
   
   1. Mark the PR as draft until it's ready to be reviewed.
   2. Always add/update tests for any changes unless you have a good reason.
   3. Always update the documentation to reflect the changes made in the PR.
   4. Make a new commit to resolve conversations instead of `push -f`.
   5. To resolve merge conflicts, merge master instead of rebasing.
   6. Use "request review" to notify the reviewer after making changes.
   7. Only a reviewer can mark a conversation as resolved.
   
   -->
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to