Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Post Refresh Request enables an environment to be refreshed to its original state after that environment has been cloned from another environment.  Post Refresh will identify all the projects that are different between the Refreshed 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, for each package-based projects, two packages will be created. First package which will be the Sync package that contains 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 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 deployed. This will bring the environment back into alignment with the state that FlexDeploy has recorded.

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

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

  • No labels