Configuration Management Projects

Configuration Management type projects are available within FlexDeploy for managing migrations through FlexDeploy packages and releases. This provides the ability to orchestrate migrations from FlexDeploy with any approvals, scheduling, and other release tasks defined in one place.

​

Initial Setup

​

Create the Project

To start running migrations from a FlexDeploy project, create a package-based project of type Configuration Management.

​

Build and Deploy Workflows

The project will need a build workflow containing the Build Migration operation and deploy workflow containing the Deploy Migration operation. See Configuration Management Operations for more information on all available operations.

​

Project Configuration

Add the new workflows within the new project configuration. Set the build and deploy target groups to run against a Localhost endpoint. On the Properties tab, set the associated Configuration Management application for the project. Optionally provide include and exclude paths to limit what plans and migrations to include in the project.

​

Topology

Navigate to the target group configured on the project. For each target, set the Configuration Management environment associated to this FlexDeploy environment. This is the environment which will be used as a source when required for initiating requests.

​

File Catalog and Packages

Once the project is configured, select Discover on the File Catalog to load all migrations for the selected application. File paths will follow the naming convention /<Plan name>/<Migration name>. After initial file discovery, migrations will be auto-discovered on creation and synced if any changes occur. After discovering, a package will automatically be created for each migration in the File Catalog. From here, these migration packages are ready to be built and deployed, or added to a release.

​

Running Configuration Management Operations

Migration packages can be built and deployed at the project level. A build execution will verify plan data is loaded for the migration(s) in the package. A deploy execution will perform the actual migration sourcing from the selected environment. Under execution steps, any requests made in Configuration Management will be shown, along with the status and a link to view more details. Migrations can also be initiated at the release level. Along with the general schedules, approvals, etc, pipelines can include utility and pre-deploy steps for performing Configuration Management operations. For more information, see Execute All Configuration Utility and Pre-Deploy All.

​

Security

When executing any Configuration Management operations at the project level, the requester must have permission to perform each corresponding request in Configuration Management. If the requester does not have permission, the request will not go through and the FlexDeploy workflow will fail. Make sure to complete setup in Configuration Management for user permissions. From release executions, security is not restricted by user. Any checks should be in place through pipeline security, approvals and other pipeline gates.

​

Manual Packages

Configuration Management manual migrations are discovered as manual packages. They are not built or deployed from the project. Include them in a release and complete them through the Deploy All step, which creates a Manual Package task for the assigned FlexDeploy or Configuration Management group. See Manual Packages for more details.