HuanXin-Chen opened a new pull request, #11436:
URL: https://github.com/apache/apisix/pull/11436

   ### Description
   
   Many enterprises are utilizing cloud services from AWS and GCP, relying on 
the secret manager provided by these platforms to handle sensitive information. 
Integrating Apache APISIX with these secret managers can streamline the process 
of using sensitive information within APISIX, enabling users to manage and 
utilize cloud-stored sensitive data more conveniently, thus enhancing the 
overall security and usability of the system.
   
   This PR has completed the support for GCP. It added the gcp.lua file to the 
original secret module, allowing users to store their secret information on GCP 
using the same reference method as before.
   
   ### 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
   - [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]

Reply via email to