Metadata driven product configuration management
A method may include: receiving a notification of a triggering event, the triggering event identifying an associated product; accessing a baseline configuration for the product; transmitting a notification to a recipient responsible for maintaining the baseline configuration for the product; receiving an approved update to the baseline configuration from the recipient; generating an updated baseline configuration for the product based on the approved update; querying a database to identify an application subscriber for the triggering event for the product; and transmitting the updated baseline configuration to the identified application subscriber.
1. A computer-implemented method comprising:
receiving a notification of a triggering event, the triggering event identifying an associated product, and the triggering event identifying an event type;
accessing a baseline configuration for the product;
transmitting, based on the triggering event and before any changes to the baseline configuration, a notification to a recipient responsible for maintaining the baseline configuration for the product, the triggering event including a vulnerability in a new version of a product in the baseline configuration;
receiving an approved update to the baseline configuration from the recipient, the approved update including restricting installation of the new version of the product until a patch is released for the product;
generating an updated baseline configuration for the product based on the approved update;
querying a database using the event type as a criterion for the querying to identify an application subscriber for the triggering event for the product; and
transmitting the updated baseline configuration to the identified application subscriber.
2. The method of claim 1 , wherein the event type is a vulnerability event for the product.
3. The method of claim 1 , wherein the triggering event is a first triggering event and the event type is a first event type, and wherein the method further includes:
receiving a second triggering event with a second event type for the product; and
wherein the updated baseline configuration includes changes based on the first and second event types.
4. The method of claim 1 , wherein receiving an approved update to the baseline configuration from the recipient includes receiving changes to operational parameters of the product.
5. The method of claim 1 , wherein at least a portion of the baseline configuration is defined according to an application-agnostic data model.
6. The method of claim 1 , further comprising:
receiving an indication from the identified application subscriber that a set of computing systems have been updated according to the updated baseline configuration.
7. The method of claim 1 , wherein the triggering event is a first triggering event, and wherein the method further includes:
receiving a second triggering event for the product; and
deduplicating the first and second triggering events by comparing product identifiers of the first and second triggering events.
8. The method of claim 1 , wherein the event type identifies a source entity of the triggering event.
9. The method of claim 1 , further comprising:
receiving a new event type indicating the patch is available for the product; and
updating the baseline configuration to indicate the new version of the product may be installed.
10. A non-transitory computer-readable medium comprising instructions, which when executed by at least one processor, configure the at least one processor to perform operations comprising:
receiving a notification of a triggering event, the triggering event identifying an associated product, and the triggering event identifying an event type;
accessing a baseline configuration for the product;
transmitting, based on the triggering event and before any changes to the baseline configuration, a notification to a recipient responsible for maintaining the baseline configuration for the product, the triggering event including a vulnerability in a new version of a product in the baseline configuration;
receiving an approved update to the baseline configuration from the recipient, the approved update including restricting installation of the new version of the product until a patch is released for the product;
generating an updated baseline configuration for the product based on the approved update;
querying a database using the event type as a criterion for the querying to identify an application subscriber for the triggering event for the product; and
transmitting the updated baseline configuration to the identified application subscriber.
11. The computer-readable medium of claim 10 wherein the event type is a vulnerability event for the product.
12. The computer-readable medium of claim 10 wherein the triggering event is a first triggering event and the event type is a first event type, and wherein the operations further include:
receiving a second triggering event with a second event type for the product; and
wherein the updated baseline configuration includes changes based on the first and second event types.
13. The computer-readable medium of claim 10 , wherein receiving an approved update to the baseline configuration from the recipient includes receiving changes to operational parameters of the product.
14. The computer-readable medium of claim 10 , wherein at least a portion of the baseline configuration is defined according to an application-agnostic data model.
15. The computer-readable medium of claim 10 , the operations further comprising:
receiving an indication from the identified application subscriber that a set of computing systems have been updated according to the updated baseline configuration.
16. The non-transitory computer-readable medium of claim 10 , the operations further comprising:
receiving a new event type indicating the patch is available for the product; and
updating the baseline configuration to indicate the new version of the product may be installed.
17. A system comprising:
at least one processor;
a storage device comprising instructions, which when executed by the at least one processor, configure the at least one processor to perform operations comprising:
receiving a notification of a triggering event, the triggering event identifying an associated product, and the triggering event identifying an event type;
accessing a baseline configuration for the product;
transmitting, based on the triggering event and before any changes to the baseline configuration, a notification to a recipient responsible for maintaining the baseline configuration for the product, the triggering event including a vulnerability in a new version of a product in the baseline configuration;
receiving an approved update to the baseline configuration from the recipient, the approved update including restricting installation of the new version of the product until a patch is released for the product;
generating an updated baseline configuration for the product based on the approved update;
querying a database using the event type as a criterion for the querying to identify an application subscriber for the triggering event for the product; and
transmitting the updated baseline configuration to the identified application subscriber.
18. The system of claim 17 , wherein receiving an approved update to the baseline configuration from the recipient includes restricting installation of a version of the product.
19. The system of claim 17 , wherein the operations further comprise:
receiving a new event type indicating the patch is available for the product; and
updating the baseline configuration to indicate the new version of the product may be installed.