lxbme opened a new pull request, #13078:
URL: https://github.com/apache/apisix/pull/13078
- Add optional parameter 'enable_type_conversion' to resolve_conf_var
function
- Disable type conversion when processing apisix.yaml in standalone mode
- Keep type conversion enabled for config.yaml to maintain backward
compatibility
- Add test cases for large numeric strings and type preservation
This fixes the issue where environment variables containing large numbers
(exceeding Lua's double precision) were automatically converted to scientific
notation in standalone mode, causing validation errors in plugins like
openid-connect.
Fixes #12932
### Description
This PR fixes the automatic type conversion issue for environment variables
in standalone mode `apisix.yaml`.
When using environment variables in `apisix.yaml` (standalone mode), numeric
string values were automatically converted to numbers. This caused issues when:
1. The numeric value exceeds Lua's double precision (e.g.,
`356002209726529540`)
2. The value is converted to scientific notation (e.g.,
`3.5600220972653e+17`)
3. Plugins requiring string types fail validation (e.g., `openid-connect`
plugin's `client_id`)
#### 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 #12932
### 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
- [ x ] I have added tests corresponding to this change
- [ x ] I have updated the documentation to reflect this change
(No documentation update needed - this is an internal bug fix with
no user-facing configuration changes)
- [ x ] 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]
