suryaparua-official commented on PR #12935: URL: https://github.com/apache/apisix/pull/12935#issuecomment-4071582086
Hi @moonming, thanks for the suggestion. I set up a local environment (WSL + OpenResty + etcd + Vault dev server) and ran the stream TLS tests to validate the behavior. From my testing: * `apisix_secret.init_worker()` only initializes the providers and does not perform any external network calls during worker startup. * Secret fetching is triggered lazily when referenced (observed during TLS handling rather than startup), so this change should not introduce startup latency. The `$ENV://` cases work as expected. For `$secret://`, the integration is triggered, but some test cases fail locally due to Vault access differences (403 on internal endpoints), so I could not fully validate the end-to-end secret fetch in this setup. Based on the above, the initialization itself remains lightweight and should not impact startup latency. Please let me know if you’d like me to align the Vault setup more closely with the CI environment or make further adjustments. -- 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]
