Skip to Content (Press Enter)
UserImage.jpg
Wan Zayd Abdullah Akil
27Views
1Comments
ODC: Are these the correct steps for cross-environment asset migration?
Question
API
ODC

Hi All,

 I've created a small app to help automate migrating applications/assets from one business environment to another. 

Currently my steps are simply, based on the selected asset, 

  1. Find its producers and eventually get an order of assets that can deploy with no dependency issues (basic out of sync or not found in target environment), 
  2. Create/update those assets in the target environment. 
  3. Publish web applications or release libraries from that list, although this part is yet to be decided.
  4. Finally, we just use the ODC portal to deploy it to production or UAT stages, or we can automate this too.
    According to ODC, the libraries are containerized with the applications, meaning that during deployment it's not a problem, but that is deployment within the same env but different stages. So, are my steps correct in migrating the libraries along with the asset, publish, then initiate normal ODC Portal deployment? or am I missing something else?
1
0
25 Feb
Copy Link
UserImage.jpg
Wan Zayd Abdullah Akil

To anyone of concern, these are the limitations...

1. If you manually move forge components to a new environment using the post asset method, it will unlink it from forge and it will be considered yours, until you install it again from forge. 

2. Yes, you should publish after posting the asset to the new target environment. 

3. If the Asset is a library, it doesn't matter if the library is released for the app to work, as long as that particular asset version is what is needed by the applications. Releasing it means to send a notification to other applications to update. You can automate releasing by tagging it after posting the asset. 

4. This means the best you can do is make sure all your components are updated, even the forge components dependencies, if the forge component uses a dependency that is outdated, the only choice is to download that component using forge instead in the target environment

5. Automating deployment is a choice, just use ODC Portal.

Moving forward hopefully there's an API to automate forge components or just straight deployment to other environments, it is cloud after all. 

1
0
02 Mar
Copy Link
Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.