Can 1-1 Ops Manager Merge process be customized?

General
, , ,
1

Hi Team,

We are using 1-1 Ops Manager as part of our application for business changes done at BOE Environment.

As part of the OOTB process we see the BOE Changes first get saved in a Branch in BOE Environment which later gets merged to an Overlay Ruleset (with a new version) in Overlay Application.

We would like to know

  1. If this can be altered to be merged directly to application artifact ruleset (instead of an Overlay Application & Ruleset)?

  2. What is the purpose of using an overlay application?

  3. As part of the process, the Main Implementation Application gets updated to a new version every time a new change is deployed? Is this Optimal?

Please share your thoughts!

Thanks!

Priyesh A

2

Hi @Priyesh

Hope you are doing well.

Here’s the information regarding your questions about 1-1 Ops Manager and BOE changes:

  1. Merging directly to application artifact ruleset:

Yes, it is possible to alter the OOTB process to merge BOE changes directly to the application artifact ruleset instead of using an overlay application and ruleset. This can be achieved by customizing the Merge to Application step in the 1-1 Ops Manager pipeline. However, there are some things to consider-Version control: Merging directly to the application ruleset might make version control and rollback more difficult.
Dependencies: If your application has dependencies on other applications, merging directly might affect those dependencies.
Testing: You need to ensure proper testing procedures are in place to validate the changes before merging them directly into the application ruleset.

  1. Purpose of using an overlay application:

Overlay applications provide several benefits:-Isolation: Changes are isolated from the main application, allowing for easier testing and rollback.
Versioning: Overlay rulesets have their own versioning, independent of the main application. This allows for better tracking of changes.
Modularity: Overlay applications can be used to modularize functionality, making it easier to manage and maintain.

  1. Main Implementation Application version update: Updating the Main Implementation Application to a new version with every deployed change is not optimal. This can lead to unnecessary versioning and complexity. It’s recommended to update the application version only when significant changes are made or when a new release is planned.

Thank You

Megha