FlexDeploy now supports architecture where customers have strict network isolation between various environments. For example, production environment (and possibly more) is setup set up such that it cannot access source control, artifact repositories and the environment itself cannot be accessed from other environments via SSH or HTTPS. This is done mostly for security reasons. Customers employing this type of setup now security architecture can install FlexDeploy inside in each of the isolated network and environments, then copy execution details in zip format from source environment to other environments. This would allow implement implementing a build once - deploy many approach and still maintain necessary security practices.

...

• FlexDeploy is installed on each isolated networkenvironment, and plugins are also installed as part of installation.

• All FlexDeploy installations participating in isolated network architecture must be at the same version. At times, even minor releases also introduce database changes, so strict version match is required.

• Source server is where builds will be executed. There will be only one such source server, but there can be one or more such target server. Target server is where builds will be imported and deployments will be executed. There can be one or more such

• Builds are executed on source server and are imported to target server(s). Builds can not be performed on target server.

• Environments, Target Groups, Projects etc. will be configured on Source the source server. Configuration export will be done for import to target server.

• Topology

  • Target Groups and Environments must be configured on the source server and imported to any target servers.

  • Environments and Property Sets must also be assigned to Target Groups on the source server and imported to target server.

  • Endpoints can be created and assigned to Targets on the target server. Also, property values can be edited for Targets on the target server.

• Projects

  • Projects can not be created or configured on the target server. Projects can only run builds on the source server, which can then be imported to the target server where they can be deployed and tested.

  • Project and folder security is managed separately on source and target servers.

• Release

  • Releases and Snapshots can be created on the target server. However, since build can not be performed on Projects on the target server, these can only be created with existing project versions.

• Pipeline

  • Pipeline must be created on target server as it will handle deployments to different endpoints than source server. Note that source server may be deploying to zero or more environments depending on isolation requirements.

• Integrations

  • Integration Providers can not be created on the target server and will be imported from the source server. Integration Instances can be created on the target server.

• Security

  • All users, groups, and permissions are managed separately on source and target servers.

• Workflows cannot be configured on target server, hence must be imported from source server.

Configuration

The following assumes that you have upgraded to use setenvoverride.sh (or setenvoverride.bat) files. If you are still using setenv.sh, then changes will be slightly different. Configurations shown below must be performed in addition to following the installation document or automated installation process.

Configure source tomcat server will following command line option.

Source environment setenvoverride.sh

FLEXAGON_FD_JAVA_ARGS="-Dflexagon.fd.isolatednw.sourceserver=true"

Configure target tomcat server with following command line option. Target server will have limited capabilities (i.e. no builds can be performed), and it will use different sequences for generated id values.

Target environment setenvoverride.sh

FLEXAGON_FD_JAVA_ARGS="-Dflexagon.fd.isolatednw.targetserver=true"

Execution

• Make sure to configure Source source environment for Projects, Environments, Target Groups etc. Additionally, map Environments with Target Groups, making sure to include isolated environments managed by target servers only.

• Perform configuration export from source server and import from Source to Target onto target as and when necessary. This export can be done by using from Administration - Admin Operations optionpage.

• Builds can be exported individually from each workflow execution page or as a group from Snapshot Release Snapshots page.

• All export files (configuration, build, snapshot etc.) should be placed in fdexports sub-folder on Server server working directory on Target target server. Files will be automatically imported and deleted on successful import.

• If you are working with snapshot export , and the release does not yet exist on the Target target server, then the release will be created as with the status set to Not Started, this . This means that snapshot is only partially imported. You must associate a pipeline to that release and then start it. Snapshot import will complete after that automatically.

...

Note that very strict security restrictions in such configurations require manual copy of files. This is mostly seen in Government-related projects., this is mainly driven by security practices of specific organizations.

Export from Source Server

FlexDeploy allows Configurations, Builds, and Snapshots to be exported. In order for these options to be enabled, FlexDeploy must be configured as an Isolated Network Source Server (see Isolated Networks Architecture). See Configuration section above.

Export

...

Export Configurations

FlexDeploy configurations can be exported which includes the topologyenvironments, target groups, workflows, and projects of the server. The user must have administrator privileges and to download the server configuration can be downloaded from the admin operations menu. To do this, go to the Admin Operations screen (Menu → Administration → Admin Operations) screen and change the operation name to : Download Configuration Zip Archive Export Configurations, then click the Download Archive Export button that appears.

...

The folder configuration export zip contains the configuration for the whole server including the topology (environments, target groups, plugins), workflows, and projects. Please see the Properties Not Exported section for items that are not included with exports.

Once the configurationis exported successfully, it can then be imported to an Isolated Network Target Server. See Isolated Networks Import Documentation.

Export Snapshots

Snapshots can be exported from any release assuming that they were initiated successfully Initiated. To do this, go navigate to the Releases screen and click on the name of a release from the folder content.

...

From here click on the View Snapshots button.

...

Then , go to the Execution tab, click on the name actions menu of a snapshot that was Initiated.

...

Lastly, and then click the Download Archive button in the top right corner to export the snapshot.

...

...

The exported snapshot will contain all of the server’s configuration at the time of the release, as well as any build executions associated with the snapshot for the projects and packages in the release. Please see the Properties Not Exported section for items that are not included with exports.

Once the snapshot is exported successfully, it can then be imported to an Isolated Network Target Server. See Isolated Networks Import Documentation.

Export Builds

Build workflow executions can be exported from any project assuming that they completed successfully. To do this, go to the executions Execution tab of a project and click on the id of a successful build.

...

The exported build will contain all related data as well as the execution data, artifacts, and package data associated with the execution. Please see the Properties Not Exported section for items that are not included with exports. Once the build is exported successfully, it can then be imported to an Isolated Network Target Server. See Isolated Networks Import Documentation.

Properties Not Exported

...

Import on Target Server

First make sure your you are using connected to a target server. Then you must take an export and put it inside of your fdexports folder, this . This may be flexdeploy<flexdeploy_home>/application/fdexports depending on how FlexDeploy was installed. To do this, you may use any file transfer tool or method available and approved by your network and security teams.

...

If FlexDeploy is running, it will automatically start the import process shortly and delete the zip file from your fdexports folder once import is completed. This may take a few minutes to get started. This same process can be done with exported builds, snapshots, or configurations. It can also do multiple different export types at once, but it may take a bit longer. Snapshots and configurations will work on an empty or full server, but an exported build may need configurations or snapshots to be imported first, as it needs an associated project to import into. Snapshots and configurations may take a long time to import

Snapshots and configurations import may take longer, but builds should be imported fairly quick.

Configurations can be imported many times as configurations change on source server. Import process will handle the import with necessary create, update, delete.

...

Snapshots will not import if there isn’t a pipeline associated with the release on the target server. To solve this problem, go to the releases page and click on the release’s id. Add release. In the top left below the releases name, hover over the pipeline symbol and click on the edit pencil, lastly select a pipeline and start click the releasecheckbox to save. Then the snapshot will finish importing automatically. For more information on associating a pipeline with a release, see the pipeline and release documentation.