A grayscale release method, device, product, equipment and medium

Abstract

The present application discloses a grayscale publishing method, apparatus, product, device and medium, including: receiving an access request sent by a client; reading a grayscale policy, which is a policy loaded from a policy configuration file, wherein the policy configuration file includes a grayscale publishing enable indication field, a policy type indication field and a matching rule field, wherein the policy indication field is used to indicate the target policy type adopted by the grayscale publishing, and the matching rule field contains matching rules corresponding to the policy type, and different policy types correspond to different matching rules, and the matching rules are created based on user characteristics; when the grayscale publishing start indication field indicates that grayscale publishing is enabled, the access request is matched based on the target matching rule corresponding to the target policy type; if the access request successfully matches the target matching rule, the access request is forwarded to the grayscale application. In this way, it can more flexibly meet user needs and improve user experience.

Description

Technical Field

[0001] The present application relates to the field of grayscale release technology, and in particular to a grayscale release method, device, product, equipment and medium. Background Art

[0002] With the rapid development of smart devices and mobile Internet, various industries provide services to users through application software. With the development of business, application software is constantly updated and iterated. Before it is put into formal use, it is necessary to verify the functions of the new version. How to effectively verify and release the functions of the new version to ensure the stability of the system and user experience has become an important issue in technological development.

[0003] At present, grayscale release is an emerging release strategy that reduces the risk of going online by gradually pushing new version functions to some users. How to reasonably conduct grayscale release and improve user experience is a problem that needs to be solved at present. Summary of the invention

[0004] In view of this, the purpose of this application is to provide a more flexible way to meet user needs and improve user experience. The specific solution is as follows:

[0005] In a first aspect, the present application discloses a grayscale release method, comprising:

[0006] Receive access requests sent by clients;

[0007] Reading a grayscale policy, wherein the grayscale policy is a policy loaded from a policy configuration file, wherein the policy configuration file includes a grayscale release enable indication field, a policy type indication field, and a matching rule field, wherein the policy indication field is used to indicate the target policy type adopted by the grayscale release, and the matching rule field includes a matching rule corresponding to the policy type, wherein different policy types correspond to different matching rules, and the matching rule is created based on user features;

[0008] When the grayscale publishing start indication field indicates that grayscale publishing is enabled, matching the access request based on a target matching rule corresponding to the target policy type;

[0009] If the access request successfully matches the target matching rule, the access request is forwarded to the grayscale application.

[0010] Optionally, matching the access request based on a target matching rule corresponding to the target policy type includes:

[0011] When the target policy type is token matching, obtaining user feature information based on the token carried in the access request;

[0012] Matching is performed based on the target matching rule corresponding to the token matching.

[0013] Optionally, the user characteristic information includes one or more of user identification information, tenant identification information, user role information, user region information, and user usage frequency information.

[0014] Optionally, matching the access request based on a target matching rule corresponding to the target policy type includes:

[0015] When the target policy type is client IP matching, matching is performed based on the client IP carried in the access request and the target matching rule corresponding to the client IP matching;

[0016] The target matching rule is a matching rule created based on the client IP that enables grayscale publishing.

[0017] Optionally, matching the access request based on a target matching rule corresponding to the target policy type includes:

[0018] When the target policy type is device type matching, matching is performed based on the device type carried in the access request and the target matching rule corresponding to the device type matching;

[0019] The target matching rule is a matching rule created based on the device type for which grayscale release is enabled.

[0020] Optionally, matching the access request based on a target matching rule corresponding to the target policy type includes:

[0021] When the target policy type is user agent matching, matching is performed based on the target matching rule corresponding to the device type matching based on the user agent information carried in the access request;

[0022] The target matching rule is a matching rule created based on user agent information that enables grayscale publishing.

[0023] Optionally, the policy configuration file further includes a protocol indication field, and forwarding the access request to the grayscale application includes:

[0024] Based on the communication protocol corresponding to the protocol indication field, the access request is forwarded to the grayscale application.

[0025] In a second aspect, the present application discloses a grayscale publishing device, comprising:

[0026] A request receiving module, used for receiving an access request sent by a client;

[0027] A policy reading module is used to read a grayscale policy, wherein the grayscale policy is a policy loaded from a policy configuration file, wherein the policy configuration file includes a grayscale release enabling indication field, a policy type indication field, and a matching rule field, wherein the policy indication field is used to indicate the target policy type adopted by the grayscale release, and the matching rule field includes a matching rule corresponding to the policy type, wherein different policy types correspond to different matching rules, and the matching rule is created based on user characteristics;

[0028] A request matching module, configured to match the access request based on a target matching rule corresponding to the target policy type when the grayscale release start indication field indicates that grayscale release is enabled;

[0029] A request forwarding module is used to forward the access request to the grayscale application if the access request successfully matches the target matching rule.

[0030] In a third aspect, the present application discloses a computer program product, which implements the aforementioned grayscale release method when executed.

[0031] In a fourth aspect, the present application discloses an electronic device, including a memory and a processor, wherein:

[0032] The memory is used to store the computer program;

[0033] The processor is used to execute the computer program to implement the aforementioned grayscale release method.

[0034] In a fifth aspect, the present application discloses a computer-readable storage medium for storing a computer program, wherein the computer program implements the aforementioned grayscale release method when executed by a processor.

[0035] It can be seen from the above scheme that the present application provides a grayscale publishing method, including: receiving an access request sent by a client; reading a grayscale policy, wherein the grayscale policy is a policy loaded from a policy configuration file, and the policy configuration file includes a grayscale publishing enable indication field, a policy type indication field, and a matching rule field, the policy indication field is used to indicate the target policy type adopted by the grayscale publishing, and the matching rule field contains the matching rules corresponding to the policy type, different policy types correspond to different matching rules, and the matching rules are created based on user characteristics; when the grayscale publishing start indication field indicates that the grayscale publishing is enabled, the access request is matched based on the target matching rule corresponding to the target policy type; if the access request successfully matches the target matching rule, the access request is forwarded to the grayscale application.

[0036] It can be seen that the beneficial effects of the present application are: the grayscale policy is configured through a policy configuration file, the policy configuration file includes a grayscale release enable indication field, a policy type indication field for indicating the policy type, and a matching rule field, different policy types correspond to different matching rules, matching rules are created based on user characteristics, and targeted grayscale release is controlled by matching rules corresponding to different policy types, which can more flexibly meet user needs and improve user experience.

[0037] Correspondingly, a grayscale release device, product, equipment and readable storage medium provided by the present application also have the above-mentioned technical effects. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying any creative work.

[0039] Figure 1 A flow chart of a grayscale publishing method provided in an embodiment of the present application;

[0040] Figure 2 A schematic diagram of grayscale release provided in an embodiment of the present application;

[0041] Figure 3 A schematic diagram of the structure of a grayscale publishing device provided in an embodiment of the present application;

[0042] Figure 4 A structural diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0043] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0044] See also Figure 1 As shown, the embodiment of the present application discloses a grayscale release method, including:

[0045] Step S11: receiving an access request sent by the client.

[0046] The grayscale publishing method provided in this embodiment can be applied to various online service platforms, such as online service platforms related to charging services, smart electric vehicle charging pile management systems, mobile payment charging applications, etc. The client can be understood as the software or device used by the user to access network resources or services. The embodiment of the present application can accept access requests sent by the client, such as charging requests.

[0047] Step S12: Read the grayscale policy, wherein the grayscale policy is a policy loaded from a policy configuration file, the policy configuration file includes a grayscale release enable indication field, a policy type indication field, and a matching rule field, the policy indication field is used to indicate the target policy type adopted by the grayscale release, the matching rule field contains the matching rules corresponding to the policy type, different policy types correspond to different matching rules, and the matching rules are created based on user characteristics.

[0048] Among them, the grayscale policy can be understood as a policy for determining the user corresponding to the grayscale release, which can include whether to enable grayscale release, policy type, and matching rules, etc., which can be loaded in the policy configuration file. The grayscale release enable indication field is a field for the user to indicate whether to enable grayscale release. The policy type may include but is not limited to token matching, client IP matching, device type matching, and user agent matching. The policy type indication field is used to indicate the target policy type adopted by the grayscale release in each matching type. In addition, matching rules can be created based on user features. User features include but are not limited to client IP, device type user agent information, and user feature information corresponding to the token. User features are information that can distinguish users from other users who do not have the feature. Matching rules can be regular expressions, matching rules corresponding to fuzzy matching, etc. Fuzzy matching is approximate matching or similarity matching, which refers to the process of finding the data item closest to the target data in a given set of data. The matching rules may include: matching rules based on wildcards, matching rules based on edit distance, etc. The policy configuration file may also include a protocol indication field, for example, indicating whether HTTPS is enabled. If it is not enabled, HTTP is used by default.

[0049] The policy configuration file can be in a preset format, such as JSON format. That is, the policy configuration file can be a JSON file, which contains the following fields: isenable (grayscale release enable indication field): indicates whether grayscale release is enabled (1 for enable, 0 for disable). Strategytype (policy type indication field): specifies the policy type (such as by device type, IP address, etc.). Matchrule (matching rule): defines the matching rule, including source type, source key, matching type, and matching value. graydomain (grayscale environment domain name indication field): specifies the secondary domain name of the grayscale environment. Usehttps (protocol indication field): indicates whether HTTPS is enabled. Among them, the source type can include: a) Header; b) Cookie; c) QueryString key-value pair; d) Request IP; e) Microservice ID; f) UserAgent; g) Token.

[0050] The source key refers to the key-value pair in the cookie or header. The matching types include equal, not equal, contain, not contain, belongs to, and regular expression. For example, the following example:

[0051] Demo (i.e. example) 1 indicates accessing the grayscale environment when the DeviceType (sourcekey) in the requested Header (sourcetype=0) is equal to (matchtype=0) ios14:

[0052] "matchrule": {

[0053] "sourcetype": 0,

[0054] "sourcekey": "DeviceType",

[0055] "matchtype": 0,

[0056] "matchvalue": "ios14"

[0057] }

[0058] Demo2 indicates accessing the grayscale environment when the requested microservice (sourcetype=4) is equal to (matchtype=0) ApiDoc-HSF-Get:

[0059] "matchrule": {

[0060] "sourcetype": 4,

[0061] "sourcekey": "SID",

[0062] "matchtype": 0,

[0063] "matchvalue": "ApiDoc-HSF-Get"

[0064] }

[0065] Demo3, Token is a very special rule that needs to be determined by accessing the backend microservice. It means that when the source type is Token (sourcetype=6), the runtime will carry the Token in the request to access an internal microservice to check whether the user ID corresponding to the Token is set to allow access to the grayscale environment

[0066] "matchrule": {

[0067] "sourcetype": 6,

[0068] "sourcekey": "",

[0069] "matchtype": 0,

[0070] "matchvalue": ""

[0071] }

[0072] For Demo3, there is no need to define a specific matchvalue (Token value) in the matching rule. Instead, the microservice is checked to read a persistent data based on the passed Token to verify whether it matches.

[0073] The following is an example of a JSON file:

[0074] json

[0075] {

[0076] "mpm": {

[0077] "isenable": 1,

[0078] "strategy": {

[0079] "strategytype": 1,

[0080] "matchrule": {

[0081] "sourcetype": 0,

[0082] "sourcekey": "DeviceType",

[0083] "matchtype": 0,

[0084] "matchvalue": "ios14"

[0085] }

[0086] },

[0087] "graydomain": "mpmhd",

[0088] "usehttps": 1

[0089] }

[0090] }

[0091] Step S13: When the grayscale publishing start indication field indicates that grayscale publishing is enabled, the access request is matched based on the target matching rule corresponding to the target policy type.

[0092] In an optional implementation, when the target policy type is token matching, user feature information is obtained based on the token carried in the access request; and matching is performed based on the target matching rule corresponding to the user feature information and the token matching.

[0093] Among them, the token is the user's unique login identification, and the corresponding user feature information can be found through the token. The user feature information includes one or more of user identification information, tenant identification information, user role information, user regional information, and user usage frequency information. The user identification information can be a user name. For example, the embodiment of the present application can determine users in a specified area as users corresponding to grayscale release, users with specified roles as users corresponding to grayscale release, and users with a usage frequency higher than a preset threshold as users corresponding to grayscale release. The token itself does not contain complete user information, including but not limited to a random number issued at login as a unique identifier, device-related information (such as the device ID of the App, the OpenID of the applet, and the current login IP of the Web framework), for users with identities, it contains a user ID (UserID), for visitors (not logged in), it does not contain a user ID and the Token expiration time (different for different device types). Since the token does not contain too much user information, with the help of the token, user information leakage can be avoided during grayscale release to ensure security.

[0094] In an optional embodiment, when the target policy type is client IP matching, a match is performed based on the client IP carried in the access request and the target matching rule corresponding to the client IP matching; wherein the target matching rule is a matching rule created based on the client IP enabling grayscale release.

[0095] In this embodiment, users in a specified IP address segment may be determined as users corresponding to the grayscale release. If the client IP carried in the request is an IP in the specified IP address segment, the match with the matching rule is successful.

[0096] In an optional implementation, when the target policy type is device type matching, a match is performed based on the device type carried in the access request and the target matching rule corresponding to the device type matching; wherein the target matching rule is a matching rule created based on the device type enabling grayscale release.

[0097] For example, an Android device can be identified as a device type that enables grayscale publishing. The request sent by the Android device carries the device type and can successfully match the matching rule. The DeviceType information in the request header or Cookie can be used to determine whether the matching rule is met.

[0098] In an optional implementation, when the target policy type is user agent matching, a match is performed based on the target matching rule corresponding to the device type matching and the user agent information carried in the access request; wherein the target matching rule is a matching rule created based on the user agent information for enabling grayscale publishing.

[0099] Among them, the user agent information (i.e., UserAgent) can provide information about the user's device and browser, which may include the operating system and version used by the user, CPU type, browser and version, browser rendering engine, browser language, browser plug-in, etc. That is, the embodiment of the present application can specify the use of corresponding user agent information through user agent matching, such as the user of a certain browser as the corresponding user of the grayscale release.

[0100] Step S14: If the access request successfully matches the target matching rule, the access request is forwarded to the grayscale application.

[0101] In an optional implementation, when the policy configuration file further includes a protocol indication field, forwarding the access request to the grayscale application includes: forwarding the access request to the grayscale application based on the communication protocol corresponding to the protocol indication field. The communication protocol may be HTTP or HTTPS, and different security requirements can be met through the protocol indication field.

[0102] In this embodiment, the grayscale application is a new version application deployed in a grayscale environment, which is an online simulation environment or a pre-release environment. The grayscale environment is a transitional environment established before the formal production environment, and is used to test and verify the new version before it is officially released. By deploying the new version to the grayscale environment, the development team can observe the performance of the new version in actual operation, collect user feedback, and promptly discover and fix potential problems. This embodiment can establish a grayscale environment similar to the real environment, including server configuration, database configuration, etc., to ensure the accuracy and reliability of the test. The new version application is deployed to the grayscale environment and restricted to be visible only to test users. The secondary domain name of the grayscale environment based on the policy configuration file forwards the access request to the grayscale environment so that the grayscale application responds to the access request.

[0103] In this embodiment, if the access request does not successfully match the target matching rule, the access request is forwarded to the formal environment so that the formal application responds to the access request.

[0104] In addition, if the grayscale release enable indication field indicates that grayscale release is not enabled, the access request is forwarded to the official environment without matching. If any exception is encountered during the matching process, the access request is forwarded to the official environment to ensure that the user experience is not affected.

[0105] It can be seen that the embodiment of the present application configures the grayscale policy through a policy configuration file. The policy configuration file includes a grayscale release enable indication field, a policy type indication field for indicating the policy type, and a matching rule field. Different policy types correspond to different matching rules. Matching rules are created based on user characteristics. Targeted grayscale release is controlled by matching rules corresponding to different policy types, which can more flexibly meet user needs and improve user experience.

[0106] With the rapid development of smart devices and mobile Internet, charging services have become an indispensable part of daily life. With the surge in the number of users, the charging service system is facing high concurrency pressure. In this environment, how to effectively verify and release new version functions to ensure system stability and user experience has become an important issue in technology development.

[0107] Taking the online service platform related to the charging business as an example, the grayscale release solution provided by this application is further explained. Through the grayscale release solution provided by this application, the new version functions are gradually pushed to some users, reducing the risk of going online. Especially in high-concurrency scenarios, it can effectively control traffic and monitor the performance of new functions, so as to adjust and optimize in time. In addition, the directional grayscale method can be controlled by multiple strategies to more flexibly meet user needs and improve user experience. It can include two parts: runtime and management. The runtime can be understood as the operation of the grayscale release solution, and the management can be understood as the policy management of grayscale release.

[0108] See also Figure 2 As shown, Figure 2 A schematic diagram of grayscale publishing provided for an embodiment of the present application. The grayscale publishing solution provided by the present application can be applied to a reverse proxy server, such as Nginx, and a software system corresponding to the grayscale publishing solution is deployed in the reverse proxy server to implement grayscale publishing. The runtime may include policy loading, policy matching, and grayscale jump. When applied to Nginx, it may specifically include Nginx starting grayscale policy loading, requesting policy matching verification, and grayscale environment access.

[0109] Nginx starts grayscale policy loading: loads the grayscale policy of the secondary domain name through a local JSON file. The JSON file contains the following fields: Grayscale release enable indication field, indicating whether grayscale release is enabled (1 for enable, 0 for disable). Policy type indication field, specifying the policy type (such as by device type, IP address, etc.). Matching rule field: defines the matching rule. Grayscale environment domain name indication field, specifying the secondary domain name of the grayscale environment. Protocol indication field, indicating whether HTTPS is enabled.

[0110] Request policy matching verification: After receiving the request, the system first confirms whether the secondary domain name corresponding to the request supports grayscale release. If not, it will jump directly to the official environment. If it does, it will perform matching verification according to different policy types: A) Client IP matching: Check the client IP through fuzzy matching or regular expression to control the request to be directed to the grayscale environment. B) Device type matching: Use the DeviceType information in the Header or Cookie to determine whether it meets the matching rules. For example, when the value corresponding to the DeviceType in the Header fuzzily matches "ios14", the grayscale environment is accessed. C) UserAgent matching: Check whether it meets the matching rules based on the UserAgent feature, supporting fuzzy matching and regular expressions. D) Token matching: Use the business Token value carried in the request to call the backend microservice to verify whether the Token supports access to the grayscale environment. If any exception is encountered during the matching process, the system will automatically access the official environment to ensure that the user experience is not affected.

[0111] Grayscale environment access: Based on the matching results, the system accesses the specified grayscale secondary domain name using HTTP or HTTPS protocol.

[0112] The management part mainly includes two parts: grayscale policy adjustment and token rule maintenance. In the following cases, the grayscale policy needs to be adjusted: New key application major version upgrade: After building the grayscale environment of the new version, set the secondary domain name of the application, enable the grayscale policy, and push the relevant policy to Nginx. Function verification success: When the grayscale release has been fully verified, upgrade the formal environment to the new version and turn off the grayscale policy. Serious problem handling: If serious problems are found in the grayscale release, the grayscale release must be turned off immediately to ensure that subsequent requests access the formal environment. Token is an important identifier of user identity, and the backend microservice can resolve the requested user information through the token. When maintaining the token rules, you can batch set which users, tenants, management companies or partners can access new grayscale functions based on key applications, effectively limit the scope of grayscale verification, and reduce the risk of new function launches.

[0113] In this way, risk control can be carried out, and the risk of launching new versions can be reduced through grayscale release, ensuring the stability of the system in high-concurrency scenarios. It can improve user experience and carry out targeted grayscale release according to user characteristics to enhance user participation and satisfaction. It can monitor and provide feedback in real time. The system can monitor the performance of new functions in real time and respond quickly to potential problems to ensure that users continue to receive high-quality services. It can have a flexible management mechanism and ensure that the system remains flexible and adaptable under the ever-changing market demands through dynamic adjustment and maintenance strategies.

[0114] The online service platform related to the charging business applied by the grayscale release solution provided in the embodiment of the present application can be a smart electric vehicle charging pile management system, a mobile payment charging application, etc. Specific application scenarios include: New version function verification: When launching new charging features (such as new payment methods, charging modes, etc.), they will be tested on some users first. Fault rollback can be performed, and when a problem occurs with a new function, it can be quickly withdrawn and switched to a stable version to ensure a seamless user experience. New functions can be experienced by users in a layered manner, and targeted grayscale releases can be performed based on the user's device type, region, frequency of use, etc., to improve user satisfaction.

[0115] See also Figure 3 As shown, the embodiment of the present application discloses a grayscale publishing device, including:

[0116] A request receiving module 11, used to receive an access request sent by a client;

[0117] A policy reading module 12 is used to read a grayscale policy, wherein the grayscale policy is a policy loaded from a policy configuration file, wherein the policy configuration file includes a grayscale release enabling indication field, a policy type indication field, and a matching rule field, wherein the policy indication field is used to indicate a target policy type adopted by the grayscale release, and the matching rule field includes a matching rule corresponding to the policy type, wherein different policy types correspond to different matching rules, and the matching rule is created based on user characteristics;

[0118] A request matching module 13, configured to match the access request based on a target matching rule corresponding to the target policy type when the grayscale release start indication field indicates that grayscale release is enabled;

[0119] The request forwarding module 14 is configured to forward the access request to the grayscale application if the access request successfully matches the target matching rule.

[0120] In an optional implementation, the request matching module 13 is specifically used to: when the target policy type is token matching, obtain user feature information based on the token carried by the access request; and match the target matching rule corresponding to the token matching based on the user feature information. The user feature information may include one or more of user identification information, tenant identification information, user role information, user region information, and user usage frequency information.

[0121] In an optional embodiment, the request matching module 13 is specifically used to: when the target policy type is client IP matching, match the target matching rule corresponding to the client IP carried in the access request with the client IP matching; wherein the target matching rule is a matching rule created based on the client IP enabling grayscale release.

[0122] In an optional embodiment, the request matching module 13 is specifically used to: when the target policy type is device type matching, match the device type carried by the access request with the target matching rule corresponding to the device type matching; wherein the target matching rule is a matching rule created based on the device type enabling grayscale release.

[0123] In an optional embodiment, the request matching module 13 is specifically used to: when the target policy type is user agent matching, match the target matching rule corresponding to the device type matching based on the user agent information carried by the access request; wherein the target matching rule is a matching rule created based on the user agent information enabling grayscale publishing.

[0124] In an optional implementation, the policy configuration file further includes a protocol indication field, and the request forwarding module 14 is specifically configured to forward the access request to the grayscale application based on the communication protocol corresponding to the protocol indication field.

[0125] It can be seen that the embodiment of the present application configures the grayscale policy through a policy configuration file. The policy configuration file includes a grayscale release enable indication field, a policy type indication field for indicating the policy type, and a matching rule field. Different policy types correspond to different matching rules. Matching rules are created based on user characteristics. Targeted grayscale release is controlled by matching rules corresponding to different policy types, which can more flexibly meet user needs and improve user experience.

[0126] Furthermore, an embodiment of the present application discloses a computer program product, which, when executed, implements the grayscale release method disclosed in the embodiment.

[0127] For the specific process of the above-mentioned grayscale release method, please refer to the corresponding content disclosed in the aforementioned embodiment, which will not be repeated here.

[0128] See also Figure 4 As shown, an embodiment of the present application discloses an electronic device 20, including a processor 21 and a memory 22; wherein the memory 22 is used to store a computer program; the processor 21 is used to execute the computer program, the grayscale release method disclosed in the above embodiment.

[0129] For the specific process of the above-mentioned grayscale release method, please refer to the corresponding content disclosed in the aforementioned embodiment, which will not be repeated here.

[0130] Furthermore, the memory 22 as a carrier for storing resources may be a read-only memory, a random access memory, a magnetic disk or an optical disk, etc., and the storage method may be temporary storage or permanent storage.

[0131] In addition, the electronic device 20 also includes a power supply 23, a communication interface 24, an input / output interface 25 and a communication bus 26; wherein the power supply 23 is used to provide working voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and an external device, and the communication protocol it follows is any communication protocol that can be applied to the technical solution of the present application, and is not specifically limited here; the input / output interface 25 is used to obtain external input data or output data to the outside world, and its specific interface type can be selected according to specific application needs, and is not specifically limited here.

[0132] Furthermore, an embodiment of the present application also discloses a computer-readable storage medium for storing a computer program, wherein the computer program, when executed by a processor, implements the grayscale release method disclosed in the aforementioned embodiment.

[0133] For the specific process of the above-mentioned grayscale release method, please refer to the corresponding content disclosed in the aforementioned embodiment, which will not be repeated here.

[0134] In this specification, each embodiment is described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the embodiments can be referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part.

[0135] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein may be implemented directly using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

[0136] The above is a detailed introduction to a grayscale release method, device, product, equipment and medium provided by the present application. Specific examples are used in this article to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea; at the same time, for general technical personnel in this field, according to the idea of ​​the present application, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

Claims

1. A grayscale release method, characterized in that: include: Receive access requests sent by clients; Reading a grayscale policy, wherein the grayscale policy is a policy loaded from a policy configuration file, wherein the policy configuration file includes a grayscale release enable indication field, a policy type indication field, and a matching rule field, wherein the policy indication field is used to indicate the target policy type adopted by the grayscale release, and the matching rule field includes a matching rule corresponding to the policy type, wherein different policy types correspond to different matching rules, and the matching rule is created based on user features; When the grayscale publishing start indication field indicates that grayscale publishing is enabled, matching the access request based on a target matching rule corresponding to the target policy type; If the access request successfully matches the target matching rule, the access request is forwarded to the grayscale application.

2. The grayscale release method according to claim 1, characterized in that: The matching the access request based on the target matching rule corresponding to the target policy type includes: When the target policy type is token matching, obtaining user feature information based on the token carried in the access request; Matching is performed based on the target matching rule corresponding to the token matching.

3. The grayscale release method according to claim 2, characterized in that: The user characteristic information includes one or more of user identification information, tenant identification information, user role information, user region information, and user usage frequency information.

4. The grayscale release method according to claim 1, characterized in that: The matching the access request based on the target matching rule corresponding to the target policy type includes: When the target policy type is client IP matching, matching is performed based on the client IP carried in the access request and the target matching rule corresponding to the client IP matching; The target matching rule is a matching rule created based on the client IP that enables grayscale publishing.

5. The grayscale release method according to claim 1, characterized in that: The matching the access request based on the target matching rule corresponding to the target policy type includes: When the target policy type is device type matching, matching is performed based on the device type carried in the access request and the target matching rule corresponding to the device type matching; The target matching rule is a matching rule created based on the device type for which grayscale release is enabled.

6. The grayscale release method according to claim 1, characterized in that: The matching the access request based on the target matching rule corresponding to the target policy type includes: When the target policy type is user agent matching, matching is performed based on the target matching rule corresponding to the device type matching based on the user agent information carried in the access request; The target matching rule is a matching rule created based on user agent information that enables grayscale publishing.

7. The grayscale release method according to any one of claims 1 to 6, characterized in that: The policy configuration file further includes a protocol indication field, and forwarding the access request to the grayscale application includes: Based on the communication protocol corresponding to the protocol indication field, the access request is forwarded to the grayscale application.

8. A grayscale publishing device, characterized in that: include: A request receiving module, used for receiving an access request sent by a client; A policy reading module is used to read a grayscale policy, wherein the grayscale policy is a policy loaded from a policy configuration file, wherein the policy configuration file includes a grayscale release enabling indication field, a policy type indication field, and a matching rule field, wherein the policy indication field is used to indicate the target policy type adopted by the grayscale release, and the matching rule field includes a matching rule corresponding to the policy type, wherein different policy types correspond to different matching rules, and the matching rule is created based on user characteristics; A request matching module, configured to match the access request based on a target matching rule corresponding to the target policy type when the grayscale release start indication field indicates that grayscale release is enabled; A request forwarding module is used to forward the access request to the grayscale application if the access request successfully matches the target matching rule.

9. A computer program product, characterized in that When the computer program product is executed, the grayscale release method according to any one of claims 1 to 7 is implemented.

10. An electronic device, characterized in that: comprising a memory and a processor, wherein: The memory is used to store the computer program; The processor is used to execute the computer program to implement the grayscale release method as described in any one of claims 1 to 7.

11. A computer-readable storage medium, characterized in that: Used to store a computer program, wherein when the computer program is executed by a processor, the grayscale release method according to any one of claims 1 to 7 is implemented.

Images