nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

DataDeploy: edition deploy instead of file deploy

Michael_Mc_OFI

Hello all, thank you in advance for any insight you provide!

OpenDeploy Version is 6.0.2.1.1
DataDeploy Version is 6.0.2.1.1

I'm currently running a process that snaps an edition in TeamSite, compares the new edition with the previous edition to generate a filelist of differences, and deploys metadata via a filelist based deployment.

The problem I'm having with the filelist based deployment is if it fails and rolls back for any reason, I have to re-run the deployment based on a specific filelist... which can be problematic if the process is automated. (and it is)

What I'd rather do is: snap a new edition, and use datadeploy to deploy the metadata for the most current edition. This would help me to keep my database in sync better, and "self correct" any missing/extra entries.

Any thoughts on how I might achieve this?

Thanks!

Find more posts tagged with

Comments

Adam Stoller

Hello all, thank you in advance for any insight you provide!

OpenDeploy Version is 6.0.2.1.1
DataDeploy Version is 6.0.2.1.1

I'm currently running a process that snaps an edition in TeamSite, compares the new edition with the previous edition to generate a filelist of differences, and deploys metadata via a filelist based deployment.

The problem I'm having with the filelist based deployment is if it fails and rolls back for any reason, I have to re-run the deployment based on a specific filelist... which can be problematic if the process is automated. (and it is)

What I'd rather do is: snap a new edition, and use datadeploy to deploy the metadata for the most current edition. This would help me to keep my database in sync better, and "self correct" any missing/extra entries.

Any thoughts on how I might achieve this?

Thanks!

I'm not sure about the specific answer - but as a possible flaw in your process - do you ensure that you are comparing the latest edition with the last deployed edition? If not, you are likely to run into problems as the difference between two subsequent editions may not contain what you're looking for.

Michael_Mc_OFI

In trying to include as much information as necessary, I may have asked a confusing question. Allow me to rephrase:

Lets say I have edition "A". I want to use DataDeploy to submit all the metadata for extended attributes for edition "A" to the database without using a file based submission. How can I accomplish this?

(thanks again!)

RajatChopra

Lets say I have edition "A". I want to use DataDeploy to submit all the metadata for extended attributes for edition "A" to the database without using a file based submission. How can I accomplish this?

(thanks again!)

I am assuming you do not want to use FILELIST based submissions for DataDeploy.

DD also lets you directly specify a directory path. DD will scan all the files, pursuant to your filter criteria, and run the deployment for those. You can also make this recursive, in which case the deployment will scan all sub-directories of the given path recursively. This path can very well be a TeamSite STAGING area or any other path you so wish within the store.

Is this the type of solution you are looking for? If no, could you possibly try to re-phrase it again?

Migrateduser

I think what Michael means is can we do edition based deployment using latest edition. So we say area=/default/main/.../EDITION in the source, then DD should pickup the latest edition automatically and deploy it.

Am I correct Michael ? I am also looking to do something similar.

RajatChopra

I think what Michael means is can we do edition based deployment using latest edition. So we say area=/default/main/.../EDITION in the source, then DD should pickup the latest edition automatically and deploy it.

Am I correct Michael ? I am also looking to do something similar.

AFAIK That is not possible. You will have to specify the exact EDITION name for DD to pick it up from there. The only exception is the EDITION and IW_PREV EDITION used on OpenDeploy scripts.