Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Post Refresh Request enables a target Post Refresh Request enables an environment to be refreshed to its original state after that target environment has been cloned from another environment.   Post Post Refresh will identify all the projects that are different between the source and targetRefreshed To and Refreshed From environments.  If a project is package-based, it will also determine which files are different between the source and target.  If there are files that are different, a package for each package-based projects, two packages will be created. First package which will be the Sync package that contains only those files.  Then the original project versions (or the newly rebuilt package for package-based projects) from the source environment will be redeployed to target environment. If the project was only deployed to the target environment, then it will be deployed again.This all the files that are deployed to the Refreshed From environment.  The second package, Refresh package will include all the files deployed to the Refreshed To environment . Files that are only deployed to the Refreshed To environment will be marked as destructive in the Sync package. The following steps are performed to complete the post refresh request.

  1. Submit build request for all package -based projects for the Sync packages.

  2. Submit build request for all package -based projects for the Refresh packages.

  3. Executes Sync State

    • For package-based projects, files inside Sync package will be applied.

    • For standard project, sync state runs using the project version of the Refreshed From environment.

  4. Executes Deploy

    • For package-based projects, file inside Refresh package will be deployed.

    • For standard project, deploys the original project version from the Refreshed To environment will be deployed.. If there is no change, deployment for standard project will be skipped.

Post Refresh feature is needed when an EBS environment such as development (Refreshed To) is cloned from production (Refreshed From).  Once the clone is complete, you can initiate the Post Refresh Requests for the target refreshed to environment.  Any changes that you have in that development environment that may have been lost because of the clone in the development environment will be redeployed in force modedeployed. This will bring the environment back into alignment with the state that FlexDeploy has recorded.

Info

Post Refresh is not compatible with package-based projects with files that are sourced from a back end system.

Viewing and Creating Post Refresh Requests 

The Post Refresh Requests button is on the Target page.  To get to the Target page, first select Topology from the menu, then select the Topology Overview section, next locate the Environment and Target Group  and click on the colored dot to go to the Target page to view or create Post Refresh Requests.

...

On Target page, click the Post Refresh Requests button on top right corner to view the Post Refresh Requests.

...

Creating A New Post Refresh Request

...

Enter values for the following fields:

...

Field Name

...

Required

...

Description

...

Refreshed From Environment

...

Yes

...

Name of the source environment that you cloned to the target.

Any projects which are not in sync between the source and the target will be redeployed to the target.

...

Requested Start Time

...

Yes

...

Start Time for the refresh deployments to begin.

Click the Find & Re-Deploy button in the top right corner to redeploy the projects.  When the Request Status is complete, the refresh is done.

Viewing Post Refresh Request Status

Below is Post Refresh Requests section which provides a history of recent Post Refresh Requests for that Target.

...

...

Request Status

...

Description

...

Pending

...

Initial status while builds are executing.

...

Deploying

...

Workflow requests for the post refresh request are being deployed.

...

Complete

...

All the workflow requests for the post refresh are either Completed, Failed, Aborted, or Rejected.

Click a Post Refresh Id to view the detailed status of a particular request.

In the below screen we are viewing the Post Refresh Status of Post Refresh Request Id 1558941

...

This page shows the Post Refresh status and workflow request status. Please refer to Build & Deploy Projects for more information about the lifecycle of a workflow request and its workflow execution. 

...

Info

Sync State is a new workflow type used for Post Refresh. When it’s executed for a Target Group and an Environment (Refreshed To), the workflow will make FlexDeploy deployment state files and projects identical to the clone(Refreshed From) environment.

Viewing Post Refresh Requests

Creating Post Refresh Request