Baseline Patching Technical Details

OS Version Compatibility

If a dependent action includes resources with OS types that weren't present in the baseline source, the patching will fail with an error. This is enforced to ensure consistency between environments.

Example:

Baseline Source:

• windows2022-1-dev
• windows2022-2-dev
• ubuntu-22.04-1-dev
• ubuntu22.04-2-dev

Dependent action:

• windows2022-1-prod
• windows2019-1-prod ← will produce an error

Package Version Resolution

When multiple resources of the same OS type in the baseline source have different versions of the same package, the latest version is chosen for the baseline snapshot.

Example:

BaselineSource:

• ubuntu22.04-1: gzip-1.23
• ubuntu22.04-2: gzip-1.24
• ubuntu22.04-3: gzip-1.23

Result: gzip-1.24 will be used (not gzip-1.23)

Batch Processing Limitations

There are specific limitations when using action batches:

• Action limitations within batches: You cannot add multiple SCAN or PATCH actions within the same batch as a baseline source. Each batch may contain only one action that serves as a baseline source.

note

This limitation exists because baseline patching is inherently sequential - first the baseline needs to be created, then applied.

Editing Limitations

When working with plans that have a baseline source defined:

1. Action order restrictions:

   • You cannot change the order of the baseline source action
   • You cannot move dependent actions above the baseline source

2. Settings inheritance:

   • When baseline source is set, all dependent actions will inherit its settings
   • Settings that were defined in dependent actions will not be automatically restored after disabling the baseline source

3. Single baseline source limitation:

   • Only one baseline source can be enabled per plan
   • This applies whether the baseline source is a standalone action or part of a batch

warning

Always review action settings manually after disabling a baseline source, as you may need to reconfigure some settings.