Partial deploy bundles

Partial deploy bundles provides a way to deploy a subset of the Softadmin® system. Partial deploy bundles should only be used for small or isolated units of functionality, otherwise complexity can easily get out of hands.

Like with regular deploys, partial deploy bundles are imported within a single database transaction, preventing half states after failed imports.

Distributing updates

All items included in the bundle will be either created or overwritten in the target system upon import. Therefore the same bundle can be imported repeatedly without causing errors. For example, if you change an existing menu item, you don't need to keep track of whether the menu item exists in the target system before you import it.

You do, however, need to make sure all new items are added to the bundle.
Let's say for example, that you have an existing menu item, and a bundle has already been created to export it. If you add (for example) an InfoSQL procedure to the menu item, then the existing bundle will not know about it, since it didn't exist when the bundle was created. In this case you must add the InfoSQL procedure to the bundle (in the "SQL modules" tab). Failing to do so with cause the import to fail, since the menu item will reference a procedure that is missing in the target database.

Limitations

Bundles only work if the source and target systems have matching Softadmin® versions, unless it contains only SQL objects and scripts.

Not all entities may be included, see the "View information" menu item for your versions status.

Futher information

For more detailed instructions, see "Partial deploy bundles" under the Deploy menu group.