Shared components for configuration data management

1 . A method comprising:

obtaining a configuration data component that is associated with a first configuration data library, wherein the configuration data component indicates one or more parameters of a software service;

providing a request for the configuration data component to be used in a second configuration data library;

linking the configuration data component with the second configuration data library such that a single instance of the configuration data component is shared by the first configuration data library and the second configuration data library;

updating the single instance of the configuration data component; and

reflecting, in the first configuration data library and the second configuration data library, updates to the single instance of the configuration data component.

2 . The method of claim 1 , further comprising:

receiving, in response to the request, approval to use the configuration data component in the second configuration data library.

3 . The method of claim 1 , further comprising:

overriding a value of a specific parameter of the configuration data component to an overridden value, wherein the specific parameter is to be used with the second configuration data library but not the first configuration data library.

4 . The method of claim 3 , wherein linking the configuration data component comprises linking the overridden value of the specific parameter to the second configuration data library but not the first configuration data library.

5 . The method of claim 1 , further comprising:

providing, to a client device by way of a graphical user interface, a representation of the configuration data component as shared, wherein the graphical user interface includes:

(i) a first menu allowing selection of the configuration data component;

(ii) a panel displaying the one or more parameters of the configuration data component; and

(iii) a second menu allowing performance of an action associated with the configuration data component, wherein the action involves including the configuration data component in a further configuration data library, including the configuration data component in an application or service, or updating the configuration data component.

6 . The method of claim 5 , further comprising:

receiving, by way of the second menu, an update request for updating the configuration data component; and

providing, by way of the graphical user interface, a pop-up window allowing the updating of the configuration data component.

7 . The method of claim 1 , wherein the configuration data component is used by an application or service.

8 . The method of claim 1 , further comprising:

providing a change request for a specific parameter of the one or more parameters to be updated to a new value; and

receiving, in response to the change request, approval to update the specific parameter.

9 . The method of claim 8 , wherein the change request includes a changeset that refers to a list of updates made to the one or more parameters as part of the change request.

10 . The method of claim 8 , further comprising:

storing, in a database, a snapshot representing a version of the one or more parameters after the one or more parameters have been updated, wherein the snapshot is a static representation of the one or more parameters at a specific time at which the snapshot was stored.

11 . The method of claim 1 , wherein the one or more parameters are stored in a database, and wherein the database includes:

a node table containing node records of types and values of the one or more parameters;

an application table containing application records associated with applications or libraries; and

a shared component table containing shared component records associated with shared configuration data components.

12 . The method of claim 11 , wherein the application records and the shared component records respectively include unique identifiers of the node records.

13 . The method of claim 11 , wherein the shared component records respectively include unique identifiers of the application records.

14 . The method of claim 11 , wherein the database further comprises:

a changeset table containing changeset records associated with changesets, and wherein at least one of the changesets refers to a list of updates made to the one or more parameters.

15 . The method of claim 14 , wherein the changeset records respectively include unique identifiers of the application records.

16 . The method of claim 14 , wherein the database further comprises:

a snapshot table containing snapshot records associated with snapshots, wherein a snapshot is a static representation of parameters at specific times at which each of the respective snapshots was stored.

17 . The method of claim 16 , wherein the snapshot records respectively include unique identifiers of the changeset records.

18 . A computing system comprising:

one or more processors;

memory; and

program instructions, stored in the memory, that upon execution by the one or more processors cause the computing system to perform operations comprising:

obtaining a configuration data component that is associated with a first configuration data library, wherein the configuration data component indicates one or more parameters of a software service;

providing a request for the configuration data component to be used in a second configuration data library;

linking the configuration data component with the second configuration data library such that a single instance of the configuration data component is shared by the first configuration data library and the second configuration data library;

updating the single instance of the configuration data component; and

reflecting, in the first configuration data library and the second configuration data library, updates to the single instance of the configuration data component.

19 . A non-transitory computer-readable medium storing program instructions that, when executed by one or more processors of a computing system, cause the computing system to perform operations comprising:

obtaining a configuration data component that is associated with a first configuration data library, wherein the configuration data component indicates one or more parameters of a software service;

providing a request for the configuration data component to be used in a second configuration data library;

linking the configuration data component with the second configuration data library such that a single instance of the configuration data component is shared by the first configuration data library and the second configuration data library;

updating the single instance of the configuration data component; and

reflecting, in the first configuration data library and the second configuration data library, updates to the single instance of the configuration data component.