Method and device for managing Nacos configuration based on IDEA plug-in and medium

Abstract

The invention relates to the technical field of software management, and provides a Nacos configuration management method and device based on an IDEA plug-in and a medium, and the method comprises the steps: responding to a Nacos management action triggered by a user, and constructing and displaying a Nacos configuration management interface based on the IDEA plug-in; responding to a first triggering operation of a user on the first area, and accessing a remote service management page corresponding to the Nacos environment configuration item in the second area through the embedded browser component; when an event monitoring mechanism built in the embedded browser component monitors that a user executes configuration release confirmation operation, obtaining current configuration content; and completing configuration release in the target environment based on the current configuration content. According to the method, the Nacos configuration management function is deeply integrated into the IDEA development environment, so that developers do not need to frequently switch among different tools, the operation process is simplified, and the development efficiency is remarkably improved.

Description

Technical Field

[0001] This disclosure relates to the field of software management technology, and more specifically, to a method, apparatus, and medium for managing Nacos configurations based on an IDEA plugin. Background Technology

[0002] In software development, configuration management is a crucial aspect of project success. With the widespread adoption of microservice architectures, configuration centers have become essential tools for centrally managing various configuration information. Nacos, as an excellent service discovery and configuration management platform, is widely used by development teams. When developing projects using an Integrated Development Environment (IDEA), developers frequently need to debug and modify project configurations to ensure correct operation in different environments and scenarios. However, existing configuration management methods have some inconveniences in handling the interaction between IDEA projects and the Nacos configuration center, impacting development efficiency.

[0003] In related technologies, when developers need to modify configurations while debugging projects in IDEA, the process is extremely cumbersome. They need to frequently switch between IDEA and their browser, logging into the Nacos console through the browser to view and modify the configurations. After the configurations take effect, they return to IDEA to continue debugging. This approach has significant drawbacks. For example, the Nacos configuration center is disconnected from the development environment (IDEA). Every time the configuration in the IDEA project is modified, it is necessary to log into the Nacos console to make the corresponding changes. This could potentially lead to configuration version inconsistencies, posing a potential risk to the project. Summary of the Invention

[0004] This disclosure provides at least one method, apparatus, and medium for managing Nacos configuration based on an IDEA plugin. By deeply integrating Nacos configuration management functionality into the IDEA development environment, developers can complete the entire process of viewing, editing, and publishing Nacos configurations within the IDEA interface without frequently switching between different tools, simplifying the operation process and significantly improving development efficiency.

[0005] This disclosure provides a method for managing Nacos configuration based on an IDEA plugin, including: In response to a user-triggered Nacos management action, a Nacos configuration management interface is built and displayed based on the IDEA plugin; wherein, the configuration management interface has a column layout, including a first area for displaying a list of at least one Nacos environment configuration item, and a second area for displaying content; In response to a user’s first trigger operation on any Nacos environment configuration item in the first region, the remote Nacos service management page corresponding to any Nacos environment configuration item is accessed in the second region via an embedded browser component. When the event listening mechanism built into the embedded browser component detects that a user performs a configuration release confirmation operation on the remote Nacos service management page, the current configuration content is obtained; and the configuration release is completed in the target environment corresponding to any Nacos environment configuration item based on the current configuration content.

[0006] In some possible embodiments, the first area also provides an entry point for adding, modifying, or deleting each Nacos environment configuration item in the Nacos environment configuration item list; the second area is also used to display and allow the user to edit the detailed environment configuration information of the Nacos environment configuration item corresponding to the triggering operation when the user triggers an operation.

[0007] In some possible embodiments, the second area is further provided with a test connection button, a save button, and a cancel button; wherein, The test connection button is used to initiate a connection verification to the Nacos server corresponding to the service address in the detailed environment configuration information currently displayed or edited in the second area; The save button is used to store the detailed environment configuration information that has been edited in the second area; The cancel button is used to close the detailed environment configuration information currently displayed or edited in the second area, and without saving any modifications to the detailed environment configuration information.

[0008] In some possible embodiments, after building and displaying the Nacos configuration management interface based on the IDEA plugin, the method further includes: In response to a second trigger operation by the user on any Nacos environment configuration item in the first region, detailed environment configuration information corresponding to the Nacos environment configuration item is loaded and displayed in the second region.

[0009] In some possible embodiments, the embedded browser component also provides a back button; In response to the user's triggering of the return button, the second area switches from displaying the remote Nacos service management page back to displaying detailed environment configuration information.

[0010] In some possible embodiments, the response to a user-triggered Nacos management action includes: The IDEA plugin stores and manages the connection information of the Nacos environment configuration items; the connection information includes at least the service address, username, and password.

[0011] In some possible embodiments, the step of publishing the configuration in the target environment corresponding to any Nacos environment configuration item based on the current configuration content includes: The system detects the list of Nacos environment configuration items stored locally. If other stored Nacos environment configuration items are detected in the list besides the target environment, a synchronization selection interface is provided to the user. Receive the synchronization range selection information made by the user in the synchronization selection interface, and based on the synchronization range selection information and the current configuration content, complete the configuration release in one or more Nacos environments indicated by the synchronization range information.

[0012] This disclosure provides a device for managing Nacos configuration based on an IDEA plugin, including: The interface display module is used to respond to Nacos management actions triggered by the user, and to build and display the Nacos configuration management interface based on the IDEA plugin; wherein, the configuration management interface has a column layout, including a first area for displaying a list of at least one Nacos environment configuration item, and a second area for displaying content; The page access module is used to respond to the user's first trigger operation on any Nacos environment configuration item in the first area, and access the remote Nacos service management page corresponding to any Nacos environment configuration item in the second area through an embedded browser component; The configuration publishing module is used to obtain the current configuration content when the user performs a configuration publishing confirmation operation on the remote Nacos service management page through the event listening mechanism built into the embedded browser component; and to complete the configuration publishing in the target environment corresponding to any Nacos environment configuration item based on the current configuration content.

[0013] In some possible embodiments, the first area also provides an entry point for adding, modifying, or deleting each Nacos environment configuration item in the Nacos environment configuration item list; the second area is also used to display and allow the user to edit the detailed environment configuration information of the Nacos environment configuration item corresponding to the triggering operation when the user triggers an operation.

[0014] In some possible embodiments, the second area is further provided with a test connection button, a save button, and a cancel button; wherein, The test connection button is used to initiate a connection verification to the Nacos server corresponding to the service address in the detailed environment configuration information currently displayed or edited in the second area; The save button is used to store the detailed environment configuration information that has been edited in the second area; The cancel button is used to close the detailed environment configuration information currently displayed or edited in the second area, and without saving any modifications to the detailed environment configuration information.

[0015] In some possible embodiments, the interface display module is further configured to: In response to a second trigger operation by the user on any Nacos environment configuration item in the first region, detailed environment configuration information corresponding to the Nacos environment configuration item is loaded and displayed in the second region.

[0016] In some possible embodiments, the embedded browser component also provides a back button; In response to the user's triggering of the return button, the second area switches from displaying the remote Nacos service management page back to displaying detailed environment configuration information.

[0017] In some possible embodiments, the interface display module is further configured to: The IDEA plugin stores and manages the connection information of the Nacos environment configuration items; the connection information includes at least the service address, username, and password.

[0018] In some possible embodiments, the configuration publishing module is specifically used for: The system detects the list of Nacos environment configuration items stored locally. If other stored Nacos environment configuration items are detected in the list besides the target environment, a synchronization selection interface is provided to the user. Receive the synchronization range selection information made by the user in the synchronization selection interface, and based on the synchronization range selection information and the current configuration content, complete the configuration release in one or more Nacos environments indicated by the synchronization range information.

[0019] This disclosure provides a computer device, including a processor, a memory, and a bus. The memory stores machine-readable instructions executable by the processor. When the computer device is running, the processor communicates with the memory via the bus. When the machine-readable instructions are executed by the processor, the IDEA plugin-based Nacos configuration method described in any of the above possible embodiments is executed.

[0020] This disclosure provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the IDEA plugin-based Nacos configuration management method as described in any of the possible embodiments above.

[0021] The method, apparatus, and medium for managing Nacos configuration based on the IDEA plugin provided in this disclosure deeply integrate Nacos configuration management functionality into the IDEA development environment. Developers no longer need to frequently switch between different tools; they can complete the entire process of viewing, editing, and publishing Nacos configurations within the IDEA interface in one stop. This greatly simplifies the operation process, significantly improves development efficiency, and reduces time loss and operational errors caused by tool switching. Simultaneously, by embedding a browser component and combining it with an event listening mechanism, seamless integration and accurate capture of user operations on the remote Nacos service management page are achieved. This ensures real-time acquisition of user configuration publishing confirmation operations while accurately obtaining the current configuration content, thereby automatically completing the configuration publishing of the target environment. This further improves the accuracy and timeliness of configuration publishing and reduces the complexity and error probability of manual operations.

[0022] To make the above-mentioned objects, features and advantages of this disclosure more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0023] To more clearly illustrate the technical solutions of the embodiments of this disclosure, the accompanying drawings referenced in the embodiments will be briefly described below. These drawings are incorporated in and constitute a part of this specification. They illustrate embodiments conforming to this disclosure and, together with the specification, serve to explain the technical solutions of this disclosure. It should be understood that the following drawings only show some embodiments of this disclosure and should not be considered as limiting the scope. Those skilled in the art can obtain other related drawings based on these drawings without creative effort.

[0024] Figure 1 A flowchart illustrating a method for managing Nacos configurations based on an IDEA plugin, provided in an embodiment of this disclosure, is shown. Figure 2 A flowchart illustrating a method for synchronously publishing Nacos environment configuration items according to an embodiment of this disclosure is shown. Figure 3 This illustration shows a schematic diagram of a Nacos configuration management device based on an IDEA plugin, provided in an embodiment of this disclosure. Figure 4 A schematic diagram of the structure of a computer device provided in an embodiment of this disclosure is shown. Detailed Implementation

[0025] To make the objectives, technical solutions, and advantages of the embodiments of this disclosure clearer, the technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this disclosure, and not all of them. The components of the embodiments of this disclosure described and shown in the accompanying drawings can generally be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of this disclosure provided in the accompanying drawings is not intended to limit the scope of the claimed disclosure, but merely represents selected embodiments of this disclosure. All other embodiments obtained by those skilled in the art based on the embodiments of this disclosure without inventive effort are within the scope of protection of this disclosure.

[0026] It should be noted that similar labels and letters in the following figures indicate similar items. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures.

[0027] In this document, the term "and / or" merely describes a relationship, indicating that three relationships can exist. For example, A and / or B can represent three cases: A alone, A and B simultaneously, and B alone. Furthermore, the term "at least one" in this document means any combination of at least two of any one or more elements. For example, including at least one of A, B, and C can mean including any one or more elements selected from the set consisting of A, B, and C.

[0028] To facilitate understanding of this embodiment, the execution subject of the IDEA plugin-based Nacos configuration management method provided in this disclosure will first be described in detail. The execution subject of the IDEA plugin-based Nacos configuration management method provided in this disclosure is a computer device. This computer device can be a terminal device or a server. The terminal device can also be a mobile device, user terminal, terminal, handheld device, computing device, vehicle-mounted device, wearable device, etc. The server can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud storage, big data, and artificial intelligence platforms. Optionally, this method can also be applied to an implementation environment composed of computer devices and servers.

[0029] The method for managing Nacos configuration based on an IDEA plugin, provided in this application, will be described in detail below with reference to the accompanying drawings. See also... Figure 1The diagram shows a flowchart of a method for managing Nacos configuration based on an IDEA plugin, provided in this embodiment of the present disclosure. The method includes the following steps S101 to S103: S101 responds to user-triggered Nacos management actions by building and displaying the Nacos configuration management interface based on the IDEA plugin.

[0030] Understandably, IDEA plugins refer to software components used in the IntelliJ IDEA integrated development environment to extend its functionality and add specific features. For example, plugins for code quality inspection and database management fall into this category. By installing these plugins, IDEA can support more diverse development tasks, such as more accurately detecting potential problems in the code and conveniently managing database connections and executing SQL statements. Nacos management actions refer to user-issued commands related to Nacos configuration management, such as clicking on Nacos configuration management options in the menu, indicating the user's intention to configure and manage Nacos. Here, Nacos refers to a dynamic service discovery, configuration, and service management platform that makes it easier to build cloud-native applications. It provides functions such as service discovery, service configuration, service metadata, and traffic management, helping developers manage various services in a microservice architecture more efficiently. For example, in a microservice architecture, various services can register and discover each other through Nacos, enabling inter-service calls; at the same time, developers can use Nacos to centrally manage configuration information for different environments, avoiding hard-coding configurations in individual services.

[0031] Specifically, in response to user-triggered Nacos management actions, an IDEA plugin can be used to build and display the Nacos configuration management interface. This interface is a visual interface for managing Nacos configurations and can employ a split-column layout. Here, a split-column layout means the interface is divided into different areas, including a first area and a second area. The first area displays a list of at least one Nacos environment configuration item. These items are configuration settings for different operating environments in Nacos, such as development, testing, and production environments. For example, in a development environment, the database connection configuration specifies the database address, username, and password used during development, while in a testing environment, the service address configuration specifies the address used for service calls during testing. The second area displays relevant content, which changes based on the user's actions. For instance, when a user selects a Nacos environment configuration item in the first area, the second area may display detailed information about that item, including key-value pairs and the effective date. When the user modifies a configuration item, the second area displays the modified content in real time for confirmation and adjustment.

[0032] Here, the first area also provides entry points for adding, modifying, and deleting Nacos environment configuration items in the Nacos environment configuration item list. When a user needs to add a Nacos environment configuration item, such as when a company sets up a new test environment and needs to configure the corresponding items in Nacos, the user only needs to find the add entry point in the first area. This entry point is usually presented as a prominent "+" button. After clicking the button, the system will pop up a small window or expand a form area on the current interface, guiding the user to enter the relevant information of the new Nacos environment configuration item, such as the environment name (e.g., "New Test Environment"), service address, port number, and other key information. After the user fills in the information and submits it, a new Nacos environment configuration item is successfully added to the list. If the user finds that the information of an existing Nacos environment configuration item is incorrect, such as the service address being entered incorrectly, and needs to modify it, then the user can find the corresponding modify entry point in the first area. This entry point is usually presented as a pencil icon or the "Modify" option in the right-click menu. After clicking, an editing window will pop up. The user can correct the error information and save it to complete the modification of the configuration item. When a Nacos environment configuration item is no longer needed, such as when a temporary development environment is no longer in use, users can find the deletion entry in the first area. This entry may be a trash can icon or a "delete" option in the right-click menu. After clicking, the system will pop up a confirmation dialog box. Once the user confirms, the configuration item will be removed from the list, thus maintaining the simplicity and accuracy of the list.

[0033] Here, the second area is also used to display and allow users to edit detailed environment configuration information for Nacos environment configuration items corresponding to the user-triggered operation. When a user selects a Nacos environment configuration item in the first area, the second area will immediately respond to this operation and display the detailed configuration information for that item. This detailed configuration information can cover multiple aspects, such as database connection configuration, which may include database type (e.g., MySQL, Oracle), database address, database name, username, password, etc.; and service call configuration, which may include service address, port number, service name, call protocol, etc. Users can edit this detailed configuration information according to their actual needs, such as changing the database password or updating the service address.

[0034] For example, in actual Nacos configuration management, users may frequently connect to different Nacos environments for configuration operations, and manually entering connection information each time is tedious and prone to errors. To improve the convenience and accuracy of user operations and reduce configuration failures caused by incorrect connection information, after a user triggers a Nacos management action, the connection information of the Nacos environment configuration items can be stored and managed through the IDEA plugin; the connection information includes at least the service address, username, and password. The plugin can encrypt and store the connection information entered by the user. When the user needs to connect to the same Nacos environment again, they only need to select the corresponding connection information from the storage, and the plugin will automatically fill it into the corresponding input box, greatly improving operational efficiency and ensuring the security of connection information, preventing the leakage of sensitive information.

[0035] In some possible embodiments, the second area also includes a test connection button, a save button, and a cancel button. The test connection button is used to initiate a connection verification to the Nacos server corresponding to the service address in the detailed environment configuration information currently displayed or edited in the second area. When a user finishes editing the detailed environment configuration information in the second area and is unsure whether the configuration is correct, especially critical information such as the service address, clicking the test connection button will cause the system to attempt to establish a connection with the corresponding Nacos server according to the user's edited configuration information. If the connection is successful, a success message will be displayed, informing the user that the currently configured service address, etc., is valid and can be used normally. If the connection fails, the reason for the failure will be displayed in detail, such as network failure, server not started, incorrect username or password, etc., allowing the user to troubleshoot and correct the configuration based on the prompts, avoiding service malfunctions due to configuration errors during actual use.

[0036] Specifically, the "Save" button stores the detailed environment configuration information edited in the second area. After modifying or adding information in the second area, and confirming its accuracy, clicking the "Save" button persistently saves the edited content to the appropriate storage medium, such as the local file system or a database. This way, when the user reopens the Nacos environment configuration item, they will see the previously saved configuration information without needing to re-enter it, improving the efficiency and convenience of configuration management. The "Cancel" button closes the currently displayed or edited detailed environment configuration information in the second area without saving any modifications. During the editing process, users may not want to save their changes for various reasons, such as discovering an error in the editing direction or having other urgent tasks to handle. In this case, clicking the "Cancel" button closes the current editing interface without saving any previously edited content, restoring the configuration item to its initial state when the user opened it, allowing the user to easily perform the correct configuration operation or handle other tasks.

[0037] For example, when creating the IDEA plugin for managing Nacos configuration, you can create a project in the IntelliJ IDEA development environment. In the project type options of the creation wizard, select the IDE Plugin type, meaning you are developing a plugin project. Next, you can set the plugin's properties, such as the plugin name (here, you can name it nacos-plugin); you can also set the plugin version number for easier version management and updates; and specify the plugin's storage path to ensure the project files are stored in a suitable location. After completing these property settings, click the Initialize button. The nacos-plugin project will be successfully created and initialized. At this point, the project directory structure will be built according to plugin development specifications, including necessary configuration files and the basic code framework.

[0038] Here, the project can use Gradle as the build tool. Gradle is a powerful and flexible build automation tool that combines the flexibility of Ant with the lifecycle management advantages of Maven. In the nacos-plugin project, Gradle can easily manage project dependencies. For example, adding dependencies on Nacos-related libraries only requires simple configuration in the build script, and Gradle can automatically download and import these dependencies, ensuring that the project can correctly use these libraries during compilation and runtime. Furthermore, Gradle supports multi-project builds. If the nacos-plugin project needs to be split into multiple sub-modules for development later, Gradle can easily manage dependencies and coordinate builds between modules. Additionally, Kotlin can be used as the development language. Kotlin is a modern, concise, and safe programming language with good interoperability with Java, allowing Kotlin and Java code to be used simultaneously in the same project. Kotlin's syntax is concise and clear, reducing code size and improving development efficiency. For example, its null safety feature effectively avoids null pointer exceptions, enhancing code robustness. Using Kotlin to develop the nacos-plugin project ensures that the plugin has good extensibility, making it easy to add new functional modules as needed. At the same time, Kotlin has good cross-version compatibility, which can adapt to different versions of IntelliJ IDEA development environment, ensuring that the plugin can run stably in different environments.

[0039] Furthermore, after creating the IDEA plugin, you can add an action called "Nacos Manage" under the Tools menu in IDEA. In IntelliJ IDEA plugin development, "An Action" is the base class used to define user-triggered actions. To add this action, you first need to create a class that inherits from "An Action," for example, named "Nacos Manage Action." In this class, override its "action Performed" method, which will be called when the user triggers the action. In the "action Performed" method, you can write specific business logic code, such as opening the Nacos configuration management interface or loading the Nacos environment configuration item list. After completing the class creation and code writing, you also need to configure it accordingly in the plugin's configuration file to register this new "Nacos Manage" action under the Tools menu in IDEA. Using this action as an entry point, users can trigger the plugin's interactive functions simply by clicking "Tools" - "NacosManage" in the IDEA menu bar. For example, a Nacos configuration management window will pop up, where users can perform various operations related to Nacos configuration management, such as viewing, modifying, and publishing configurations. This allows users to conveniently and quickly use the functions provided by the plugin to manage Nacos configurations.

[0040] S102, in response to the user's first trigger operation on any Nacos environment configuration item in the first region, the remote Nacos service management page corresponding to any Nacos environment configuration item is accessed in the second region through an embedded browser component.

[0041] Understandably, the first triggering operation could be a user clicking on a Nacos environment configuration item in the first area, indicating that the user wants to further manage that configuration item. An embedded browser component is a component integrated within an application that simulates browser functionality, allowing direct access to web page content within the application without opening an external browser. For example, some software integrates an embedded browser for viewing online documents, allowing users to browse documents directly within the software without being redirected to an external browser. In this disclosure, the embedded browser component automatically initiates an access request to the remote Nacos service management page corresponding to the clicked Nacos environment configuration item, deployed on a remote server. The remote Nacos service management page is a web interface deployed on a remote server for managing Nacos services. Users can perform various Nacos configuration management operations on this page, such as creating and modifying configurations, like adding a new configuration key-value pair or modifying existing configuration values.

[0042] To further enhance user experience and ease of use, the embedded browser component provides a back button. After completing a series of management operations on the remote Nacos service management page—for example, modifying configurations or viewing necessary information—and wanting to return to the previous detailed environment configuration information interface to continue other operations, the user can trigger the back button. In response to the user's triggering of the back button, the system quickly switches the second area from displaying the remote Nacos service management page back to displaying the detailed environment configuration information. This smooth and natural switching process allows users to easily transition between different interfaces, greatly improving the efficiency and convenience of Nacos configuration management.

[0043] Here, you can use the JBCefBrowser embedded browser to access the Nacos page. JBCefBrowser is a browser component implemented by JetBrains in the IntelliJ platform based on JCEF. It has powerful functions and good compatibility, and can stably load and display the remote Nacos service management page, providing users with a browsing experience similar to that of an external browser. Alternatively, you can use HTTPAPI + custom forms to directly retrieve and display remote configurations. This involves communicating with the remote Nacos server via HTTPAPI to obtain configuration data, and then displaying these configurations in the application in the form of custom forms. This method allows for flexible customization of the display interface and interaction methods according to user needs, providing a more personalized configuration management experience. No specific limitations are specified here.

[0044] In some possible embodiments, the interaction logic between the user and the Nacos configuration management plugin can be further optimized to enhance the flexibility and convenience of operation. When the plugin is in a normal display state, i.e., the first area clearly displays the list of Nacos environment configuration items and the second area is blank or in a default prompt state, in response to the user's second trigger operation on any Nacos environment configuration item in the first area, the detailed environment configuration information corresponding to any Nacos environment configuration item is loaded and displayed in the second area.

[0045] Specifically, in real-world usage scenarios, after a user opens the plugin, the first area displays all Nacos environment configuration items in a list format. Each configuration item may include brief information such as its name and the type of environment it belongs to (e.g., development environment, testing environment, production environment). If a user wants to view detailed configuration information for a specific Nacos environment configuration item, such as its corresponding database connection parameters, service registration address, security authentication information, etc., they can execute the second trigger operation.

[0046] Here, the first triggering operation mentioned above could be a double-click operation by the user on a Nacos environment configuration item in the first area. When the user quickly double-clicks the target configuration item, the plugin will recognize this operation and access the remote Nacos service management page corresponding to that configuration item in the second area through an embedded browser component. This allows the user to perform more advanced management operations directly within the plugin, such as real-time monitoring of service status and batch modification of configurations. The second triggering operation mentioned above could be a single click operation by the user on the configuration item. When the user clicks the target configuration item, the plugin will quickly load and display the detailed environment configuration information corresponding to that configuration item in the second area. This information will be displayed in a clear and organized form, possibly using tables, columns, etc., to facilitate the user's quick browsing and retrieval of the required content.

[0047] In some other embodiments, to cater to different user habits and operational preferences, a right-click menu or toolbar button can be used to switch between editing and browsing modes. For example, when a user selects a Nacos environment configuration item in the first area and right-clicks the item, a right-click menu will pop up, containing options such as "Edit Mode" and "Browse Mode." When the user selects "Edit Mode," the second area will display detailed environment configuration information in an editable format, allowing the user to directly modify various parameters on the interface. When selecting "Browse Mode," the second area will display information in a read-only format, allowing the user to view but not modify it. Similarly, corresponding buttons can be set in the plugin's toolbar, allowing users to quickly switch between editing and browsing modes by clicking these buttons. Without specific limitations, the purpose of this design is to provide users with diverse operating methods, allowing them to choose the most suitable method according to their needs and usage scenarios, thereby improving the overall user experience and work efficiency.

[0048] S103, when the event listening mechanism built into the embedded browser component detects that the user performs a configuration release confirmation operation on the remote Nacos service management page, the current configuration content is obtained; and the configuration release in the target environment corresponding to any Nacos environment configuration item is completed based on the current configuration content.

[0049] Here, the event listener mechanism is a technical means used to monitor the occurrence of specific events. Within the embedded browser component, it can monitor various user actions on the webpage, such as clicking buttons and entering text. In this step, the event listener mechanism built into the embedded browser component monitors the user's configuration release confirmation operation on the remote Nacos service management page. For example, if a user clicks the "Publish" button, this indicates that the user wants to apply the currently set configuration to the actual environment. The current configuration content refers to the configuration information set and prepared for release by the user on the remote Nacos service management page. This may include key-value pairs and the scope of the configuration, such as setting a configuration item with the key "database.url" and the value being a specific database connection address. The target environment refers to the actual operating environment corresponding to the Nacos environment configuration item, such as a development environment, testing environment, or production environment. Completing the configuration release means applying the current configuration content to the target environment, enabling applications in that environment to run according to the new configuration. For example, after applying the new database configuration in the production environment, the applications in the production environment will use the new database connection information for data interaction.

[0050] Here, the event listening mechanism in the embedded browser component can be implemented through methods such as JS injection or establishing a specific communication protocol with the remote page to capture key user actions (such as "Publish" and "Confirm Publish" buttons) on the remote page in real time. No specific limitations are specified here. JS injection allows specific JavaScript code to be inserted into the remote Nacos service management page. This code can listen for button click events and other operations on the page, and pass the relevant information to the embedded browser component. Establishing a specific communication protocol with the remote page allows the embedded browser component and the remote page to interact with data according to agreed-upon rules. When the user performs a configuration publish confirmation operation on the remote page, the remote page will send the operation information to the embedded browser component according to the protocol, thereby triggering the subsequent process of retrieving configuration content and completing the configuration publish.

[0051] In some other embodiments, configuration publishing actions can also be captured by intercepting HTTP requests / proxying, instead of directly listening for buttons on the page; this is not specifically limited here. In this mode, the embedded browser component acts like a smart gateway, intercepting and analyzing HTTP requests between the user and the remote Nacos service management page. When the user performs a configuration publishing operation, a corresponding HTTP request is triggered, such as a POST request to send configuration data to the server. After intercepting this request, the embedded browser component carefully examines the content and purpose of the request to determine if it is a configuration publishing action. Once it is confirmed to be a configuration publishing request, it extracts key information from the request, such as configuration content and target environment, thereby triggering the subsequent configuration publishing process. The advantage of this approach is that it is independent of the specific implementation of the page. Even if the button structure or interaction method of the remote page changes, as long as the format and content of the HTTP request meet expectations, the configuration publishing action can still be accurately captured, improving the system's compatibility and stability.

[0052] For example, in real-world Nacos configuration management scenarios, different development, testing, and production environments often have their own independent configuration requirements, but some configuration information may be reused or updated synchronously across environments. For instance, after adjusting the timeout configuration of a service in the development environment, the testing and production environments may also need to update this configuration synchronously to ensure consistent service behavior across different environments. Alternatively, some basic configurations, such as database connection pool size and log levels, may only require minor adjustments to parameter values ​​in different environments, while the overall configuration structure remains the same. Therefore, to meet these complex and flexible configuration synchronization needs, improve the efficiency and accuracy of configuration management, and avoid omissions or errors caused by manually configuring each environment individually, refer to... Figure 2As shown, when publishing the configuration in the target environment corresponding to any Nacos environment configuration item based on the current configuration content, the following steps S201~S202 may be included: S201, the list of Nacos environment configuration items stored locally is checked. If other stored Nacos environment configuration items are detected in the list of Nacos environment configuration items besides the target environment, a synchronization selection interface is provided to the user.

[0053] Understandably, the locally stored list of Nacos environment configuration items is a collection of various environment configuration information that the user has previously added and saved. It records the Nacos service-related configurations under different environments. During the detection of this list, each configuration item can be iterated. When other stored Nacos environment configuration items are detected besides the target environment, it means that other environments may also need to have their configurations updated synchronously. At this point, a synchronization selection interface can be provided to the user. This interface can be presented as a pop-up window or a new page area. This interface will list all other stored Nacos environment configuration items besides the target environment. Each environment item may also have some brief information next to it, such as environment type (development, testing, production, etc.) and environment name, to facilitate quick identification and selection by the user. Simultaneously, the interface will also provide operation buttons such as select all, deselect, confirm, and cancel, allowing users to easily perform selection operations.

[0054] S202, receive the synchronization range selection information made by the user in the synchronization selection interface, and based on the synchronization range selection information and the current configuration content, complete the configuration release in one or more Nacos environments indicated by the synchronization range information.

[0055] Specifically, users select one or more environments to be synchronized on the synchronization selection interface, based on their actual needs. For example, a user might only want to synchronize the configuration to the test and pre-release environments, in which case they would only select the options corresponding to these two environments. After receiving the user's selection information, the system parses and processes it, and then, based on the synchronization scope selection information and the current configuration content, completes the configuration release in one or more Nacos environments indicated by the synchronization scope information.

[0056] For example, configuration content currently prepared for publication in the target environment can be published one by one to other corresponding Nacos environments according to the synchronization scope selected by the user. During the publication process, a series of verification and check operations can be performed to ensure that the configuration content takes effect correctly in each environment and that there are no configuration errors or conflicts caused by environment differences. For example, it can be checked whether the configuration parameters of the target environment are applicable in other environments. If incompatibility is found, timely feedback should be provided to the user so that they can make adjustments or confirm. In this way, a single operation can be linked to multiple environment updates, solving the inefficiency of repeatedly logging in and publishing one by one in multiple environments. This achieves flexible and efficient configuration synchronization and publication, improving the quality and efficiency of Nacos configuration management.

[0057] In some other embodiments, predefined rules can be used for automatic synchronization, such as directly synchronizing to a specified environment based on configuration aliases or groups, without requiring additional user confirmation. For example, users can predefine some rules to automatically synchronize configurations with certain names or groups to development, testing, and production environments. When a configuration is released in the target environment, it can be automatically synchronized to the corresponding environment according to these predefined rules, further improving the automation and efficiency of configuration synchronization.

[0058] In some other embodiments, the IDEA plugin proposed in this disclosure can also be applied to other functional modules, preferably for quick access to different Nacos environments in Run / Debug Configurations, thereby improving development and debugging efficiency. During development, developers often need to debug in different Nacos environments. Traditional methods require manually switching environment configurations, which is cumbersome and prone to errors. However, with this IDEA plugin, developers can directly select different Nacos environment configuration items in Run / Debug Configurations. The plugin automatically connects the application to the corresponding environment and loads the relevant configuration information, enabling developers to quickly and accurately develop and debug in different environments, improving the efficiency and quality of development and debugging.

[0059] The method, apparatus, and medium for managing Nacos configuration based on the IDEA plugin provided in this disclosure deeply integrate Nacos configuration management functionality into the IDEA development environment. Developers no longer need to frequently switch between different tools; they can complete the entire process of viewing, editing, and publishing Nacos configurations within the IDEA interface in one stop. This greatly simplifies the operation process, significantly improves development efficiency, and reduces time loss and operational errors caused by tool switching. Simultaneously, by embedding a browser component and combining it with an event listening mechanism, seamless integration and accurate capture of user operations on the remote Nacos service management page are achieved. This ensures real-time acquisition of user configuration publishing confirmation operations while accurately obtaining the current configuration content, thereby automatically completing the configuration publishing of the target environment. This further improves the accuracy and timeliness of configuration publishing and reduces the complexity and error probability of manual operations.

[0060] Those skilled in the art will understand that, in the above-described method of the specific implementation, the order in which each step is written does not imply a strict execution order and does not constitute any limitation on the implementation process. The specific execution order of each step should be determined by its function and possible internal logic.

[0061] Based on the same inventive concept, this disclosure also provides an IDEA plugin-based Nacos configuration management device corresponding to the IDEA plugin-based Nacos configuration management method. Since the principle of the device in this disclosure for solving the problem is similar to the above-mentioned IDEA plugin-based Nacos configuration management method in this disclosure, the implementation of the device can refer to the implementation of the method, and the repeated parts will not be described again.

[0062] Reference Figure 3 The diagram shown is a schematic of a Nacos configuration management device 300 based on an IDEA plugin according to an embodiment of this disclosure. The device includes: The interface display module 301 is used to respond to Nacos management actions triggered by the user, and to build and display the Nacos configuration management interface based on the IDEA plugin; wherein, the configuration management interface has a column layout, including a first area for displaying a list of at least one Nacos environment configuration item, and a second area for displaying content; Page access module 302 is used to respond to a user's first trigger operation on any Nacos environment configuration item in the first area, and access the remote Nacos service management page corresponding to any Nacos environment configuration item in the second area through an embedded browser component; The configuration publishing module 303 is used to obtain the current configuration content when the user performs a configuration publishing confirmation operation on the remote Nacos service management page through the event listening mechanism built into the embedded browser component; and to complete the configuration publishing in the target environment corresponding to any Nacos environment configuration item based on the current configuration content.

[0063] In some possible embodiments, the first area also provides an entry point for adding, modifying, or deleting each Nacos environment configuration item in the Nacos environment configuration item list; the second area is also used to display and allow the user to edit the detailed environment configuration information of the Nacos environment configuration item corresponding to the triggering operation when the user triggers an operation.

[0064] In some possible embodiments, the second area is further provided with a test connection button, a save button, and a cancel button; wherein, The test connection button is used to initiate a connection verification to the Nacos server corresponding to the service address in the detailed environment configuration information currently displayed or edited in the second area; The save button is used to store the detailed environment configuration information that has been edited in the second area; The cancel button is used to close the detailed environment configuration information currently displayed or edited in the second area, and without saving any modifications to the detailed environment configuration information.

[0065] In some possible embodiments, the interface display module 301 is further configured to: In response to a second trigger operation by the user on any Nacos environment configuration item in the first region, detailed environment configuration information corresponding to the Nacos environment configuration item is loaded and displayed in the second region.

[0066] In some possible embodiments, the embedded browser component also provides a back button; In response to the user's triggering of the return button, the second area switches from displaying the remote Nacos service management page back to displaying detailed environment configuration information.

[0067] In some possible embodiments, the interface display module 301 is further configured to: The IDEA plugin stores and manages the connection information of the Nacos environment configuration items; the connection information includes at least the service address, username, and password.

[0068] In some possible embodiments, the configuration publishing module 303 is specifically used for: The system detects the list of Nacos environment configuration items stored locally. If other stored Nacos environment configuration items are detected in the list besides the target environment, a synchronization selection interface is provided to the user. Receive the synchronization range selection information made by the user in the synchronization selection interface, and based on the synchronization range selection information and the current configuration content, complete the configuration release in one or more Nacos environments indicated by the synchronization range information.

[0069] Based on the same technical concept, this disclosure also provides a computer device. (See also...) Figure 4 The diagram shown is a structural schematic of a computer device 400 provided in an embodiment of this disclosure, including a processor 401, a memory 402, and a bus 403. The memory 402 is used to store execution instructions and includes a main memory 4021 and an external memory 4022. The main memory 4021, also called internal memory, is used to temporarily store computational data in the processor 401, as well as data exchanged with external memory 4022 such as a hard disk. The processor 401 exchanges data with the external memory 4022 through the main memory 4021.

[0070] In this embodiment, the memory 402 is specifically used to store application code that executes the solution of this application, and its execution is controlled by the processor 401. That is, when the computer device 400 is running, the processor 401 communicates with the memory 402 through the bus 403, so that the processor 401 executes the application code stored in the memory 402, and then executes the method described in any of the foregoing embodiments.

[0071] The memory 402 may be, but is not limited to, random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), etc.

[0072] Processor 401 may be an integrated circuit chip with signal processing capabilities. The aforementioned processor can be a general-purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc.; it can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this invention. The general-purpose processor can be a microprocessor or any conventional processor.

[0073] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the computer device 400. In other embodiments of this application, the computer device 400 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0074] This disclosure also provides a computer-readable storage medium storing a computer program. When a processor runs this computer program, it executes the steps of the IDEA plugin-based Nacos configuration management method described in the above-described method embodiments. The storage medium can be volatile or non-volatile computer-readable storage.

[0075] This disclosure also provides a computer program product carrying program code. The program code includes instructions that can be used to execute the steps of the method for managing Nacos configuration based on IDEA plugins described in the above method embodiments. For details, please refer to the above method embodiments, which will not be repeated here.

[0076] The aforementioned computer program product can be implemented through hardware, software, or a combination thereof. In one optional embodiment, the computer program product is specifically embodied in a computer storage medium; in another optional embodiment, the computer program product is specifically embodied in a software product, such as a software development kit (SDK), etc.

[0077] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems and devices described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. In the several embodiments provided in this disclosure, it should be understood that the disclosed systems and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division; in actual implementation, there may be other division methods. Furthermore, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Another point is that the displayed or discussed mutual coupling or direct coupling or communication connection may be through some communication interfaces; the indirect coupling or communication connection of devices or units may be electrical, mechanical, or other forms.

[0078] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0079] In addition, the functional units in the various embodiments of this disclosure can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0080] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a processor-executable, non-volatile, computer-readable storage medium. Based on this understanding, the technical solution of this disclosure, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this disclosure. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0081] Finally, it should be noted that the above-described embodiments are merely specific implementations of this disclosure, used to illustrate the technical solutions of this disclosure, and not to limit it. The protection scope of this disclosure is not limited thereto. Although this disclosure has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that any person skilled in the art can still modify or easily conceive of changes to the technical solutions described in the foregoing embodiments, or make equivalent substitutions for some of the technical features, within the scope of the technology disclosed in this disclosure. Such modifications, changes, or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this disclosure, and should all be covered within the protection scope of this disclosure. Therefore, the protection scope of this disclosure should be determined by the protection scope of the claims.

Claims

1. An Nacos configuration management method based on an IDEA plug-in, characterized in that, Comprise: In response to a user triggered Nacos management action, a Nacos configuration management interface is constructed and displayed based on an IDEA plug-in; wherein the configuration management interface has a column layout, including a first area for displaying a list of at least one Nacos environment configuration item, and a second area for displaying content; In response to a user's first trigger operation on any Nacos environment configuration item in the first area, the second area accesses the remote Nacos service management page corresponding to the any Nacos environment configuration item through an embedded browser component; When the event listening mechanism embedded in the embedded browser component listens to the user's configuration publishing confirmation operation in the remote Nacos service management page, the current configuration content is obtained; and based on the current configuration content, the configuration publishing in the target environment corresponding to the any Nacos environment configuration item is completed.

2. The method of claim 1, wherein, The first area also provides operation entrances for adding, modifying, and deleting each Nacos environment configuration item in the Nacos environment configuration item list; the second area is also used to display and edit the environment detailed configuration information of the Nacos environment configuration item corresponding to the trigger operation under user trigger operation.

3. The method of claim 2, wherein, The second area is also provided with a test connection button, a save button and a cancel button; wherein, The test connection button is used to initiate a connection verification to the Nacos server corresponding to the service address based on the environment detailed configuration information currently displayed or edited in the second area; The save button is used to store the environment detailed configuration information edited in the second area; The cancel button is used to close the environment detailed configuration information currently displayed or edited in the second area, and does not save the modification of the environment detailed configuration information.

4. The method of claim 2, wherein, After the Nacos configuration management interface is constructed and displayed based on the IDEA plug-in, it further comprises: In response to a user's second trigger operation on any Nacos environment configuration item in the first area, the second area loads and displays the environment detailed configuration information corresponding to the any Nacos environment configuration item.

5. The method of claim 2, wherein, The embedded browser component also provides a return button; In response to a user's trigger operation on the return button, the second area switches back from displaying the remote Nacos service management page to displaying the environment detailed configuration information.

6. The method of claim 1, wherein, After the response to the user triggered Nacos management action, it comprises: The IDEA plug-in stores and manages the connection information of the Nacos environment configuration item; wherein the connection information at least includes service address, username and password.

7. The method of claim 6, wherein, The configuration publishing in the target environment corresponding to the any Nacos environment configuration item based on the current configuration content comprises: Detecting the locally stored Nacos environment configuration item list, when detecting that there are other stored Nacos environment configuration items in the Nacos environment configuration item list except the target environment, providing a synchronization selection interface to the user; Receiving a synchronization range selection information made by the user in the synchronization selection interface, and based on the synchronization range selection information and the current configuration content, completing the configuration publishing in one or more Nacos environments indicated by the synchronization range information.

8. An Nacos configuration management device based on IDEA plug-in, characterized in that, Comprise: An interface display module, configured to construct and display a Nacos configuration management interface based on the IDEA plug-in in response to a Nacos management action triggered by a user; wherein the configuration management interface has a column layout, including a first area for displaying a list of at least one Nacos environment configuration item, and a second area for displaying content; A page access module, configured to access a remote Nacos service management page corresponding to any Nacos environment configuration item in the second area through an embedded browser component in response to a first trigger operation of the user on the any Nacos environment configuration item in the first area; A configuration publishing module, configured to obtain the current configuration content when a configuration publishing confirmation operation is executed by the user in the remote Nacos service management page through an event listening mechanism embedded in the embedded browser component; and complete the configuration publishing in a target environment corresponding to the any Nacos environment configuration item based on the current configuration content.

9. A storage medium having stored thereon a computer program, characterized in that The computer program is executed by the processor to implement the method of any one of claims 1-7.

10. A computer device comprising a storage medium, a processor, and a computer program stored on the storage medium and executable on the processor, characterized in that, The processor executes the computer program to implement the method of any one of claims 1-7.

Images