Description

In v8.3, LogicNets introduced this functionality as part of the Deployment Manager. It adds support for publishing package names using startcode prefixes and postfixes in the Deployment Manager. 

Used With: This function is used in the Deployment Manager.

Details

When you set the deployment configuration in the Deployment Manager you can configure prefix and postfix labels that the system will apply to all package names, startcodes, and libraries in the configuration as part of the image, giving you greater control of what gets updated. This allows you to create updated or differentiated versions of an application without overwriting previous ones. The system also applies the prefix and postfix to associated frameworks in the package.

With this function, you do not need to edit the start codes in your published projects and can still publish a unique version of the same application. You can also update related library applications and publish them without having to update the link between a project and a library. 

As an example, say you have a shared workspace with the following projects:

• Library A
• Library B
• Framework C
• Framework D, which is based on Framework C.
• App E, which is based on Framework D and has two library links to package Library A and Library B. It also has startcode appe.

Your deployment configuration looks like this:

Note: "Framework C" is not part of the configuration. 

Before the prefix and postfix support, the resulting package list in the deployment image would look like the following:

• LibraryA
• LibraryB
• FrameworkD and it is dependent on FrameworkC
• AppE with start code "start" and it is dependent on FrameworkD, FrameworkC, LibraryA, LibraryB

With the prefix and postfix functionality, you can create new packages with prefixes and postfixes; for example, you could use a prefix of apps/V1/ and startcode postfix of V1. The resulting packages would look as follows:

• apps/V1/LibraryA
• apps/V1/LibraryB
• apps/V1/FrameworkD and it is dependent on FrameworkC
• apps/V1/AppE with startcode startV1 and it is dependent on apps/V1/FrameworkD, FrameworkC, apps/V1/LibraryA, apps/V1/LibraryB

Since FrameworkC is not part of this configuration, the system does not update the framework dependency of FrameworkC in the Framework D project. To remind you in this case, the deployment editor displays a warning that a dependent package is not part of the configuration.

Create a New Configuration 

1. Add a new configuration by clicking the + sign on the left side panel in the Deployment Manager. The system opens a popup window. 
2. Enter the configuration name and optional description details. Note that the configuration name must be unique, and it can only contain lowercase letters, numbers, underscores, hyphens, and a dot. The system stores this configuration name in the manifest table in the registry.
3. Click the + icon in the green icon below the line to add an additional line. Once you have completed entering your information, click Create.

The system displays a list of all configured design instances on the dashboard in the Instance dropdown menu. Using this dropdown menu, add the list of projects and their version to the configuration screen. The system displays the available list of repositories in the repository dropdown based on the instance you select. 

You can choose the project and version to be deployed, and the system auto-populates the start code, framework, library projects, and package name field. You can change the package name, as needed, and package names can consist of lowercase letters, numbers, hyphens, underscores, or a dot. The system displays any validation errors. 

Modify Configuration

You can modify an existing configuration, including modifying, adding, or deleting the package and startcode prefix and postfix values. When you save the configuration update, the system updates the package name, library projects, framework, and startcode with these new values.

Create Image

Deploy Image