Asset Migration Streamlit Application

[bikash_rout]

• Overview
• Architecture & Workflow
• System Requirements
• Dependencies
• Application Features
• Installation & Deployment
• Sidebar Configuration & Input Fields
• 1. Instance Connectivity Settings
• 2. Execution Parameters
• 3. Assets in Scope
• 4. Group Access Control
• Code
• Screenshots

Overview

The Incorta Asset Migration App is a Streamlit-based utility designed to automate the movement of Incorta objects (Schemas, Business Schemas, Data Sources, and Dashboards) between environments (e.g., Dev to Prod). It leverages the Incorta Command Line Interface (CLI) to ensure consistent, error-free deployments.

Architecture & Workflow

The app acts as a GUI wrapper around Incorta's backend migration utilities.

• Source Instance: The environment where assets are currently located.
• Target Instance: The destination environment for the migration.
• Staging Area: A local directory where exported .zip bundles are stored before being pushed to the target. The directory is created under script directory as output/run_<YYYYMMDD>_<HHMMSS>

apps/
└── output/
└── run_20260327_120000/
├── schemas.zip
├── business_schemas.zip
├── dashboards.zip
└── load_plans.zip

System Requirements

• Python Version: 3.12.12
• Hosting: Linux OS / Mac OS / Windows OS with network access to both Incorta instances.

Dependencies

To ensure the app runs correctly in a new environment, the following dependencies must be present.

• pandas==2.3.3
• requests==2.32.5
• streamlit==1.55.0

Application Features

Feature	Description
Bulk Export	Select multiple schemas or dashboards and export them into an asset specific migration bundle
Box Path Update	If source and target use different box paths, you can use the feature to update the box path before importing it to target
Table SQL Query Update	You can use this feature to update text in a SQL query for a table
Assigning Permissions to Groups	Permissions can be assigned to assets in scope after objects are imported to target instance
History Log	Logs are put in the console screen in the UI. There is a button to download the scripts for future reference

Installation & Deployment

To deploy this app:

1. Prepare the Folder: Copy the app files to a script directory
2. Install Environment:
   pip install -r requirements.txt
   or
   python -m pip install -r requirements.txt
3. Run:
   streamlit run app.py 
   or 
   python -m streamlit run app.py

Sidebar Configuration & Input Fields

The sidebar is designed to capture all necessary metadata to authenticate and route your migration bundles. Below is a breakdown of the interactive fields:

1. Instance Connectivity Settings

These fields establish the bridge between your environments.

• Source Environment
  • URL: The full address of the "Origin" Incorta instance (e.g., https://dev.incorta.com/incorta).
  • Tenant: Tenant Name
  • User: User login
  • Pwd: Password for user
• Target Environment URL
  • URL: The destination address where assets will be deployed (e.g., https://prod.incorta.com/incorta).
  • Tenant: Tenant Name
  • User: User login
  • Pwd: Password for user

2. Execution Parameters

Final controls before triggering the backend script.

• Overwrite Assets
  • If selected, existing assets will be overwritten during the import process.
  • If not selected, assets that already exist will be skipped.
• Include Scheduler Jobs
  • If selected, associated scheduler jobs will be exported as part of the dashboard export process
  • If not selected, associated scheduler jobs will be skipped
• Include Bookmarks
  • If selected, associated bookmarks will be exported as part of the dashboard export process
  • If not selected, associated bookmarks will be skipped
• Update Box Connection
  • If selected, users will be be able to replace the box path
    • Find String: this will be searched in the exported schema xmls
    • Replace String: this will be replaced in the exported schema xmls
  • If not selected, the update box connection step will be skipped
• Update Table Query
  • If selected, users will be be able to replace text in the table queries
    • Find String: this will be searched in the exported schema xmls
    • Replace String: this will be replaced in the exported schema xmls
  • If not selected, update table queries will be skipped.

3. Assets in Scope

This section filters exactly what you want to move.

• Schema(s)
  • Input comma separated schema names
  • e.g. _DateCommon,_IncortaMetadata,_InspectorMetadata
• Business Schema(s)
  • Input comma separated business schema names
  • e.g. _incorta,GeneralLedger
• Dashboard(s)
  • Input comma separated dashboard names or folder names with full path
  • e.g. /Incorta Tools/Observability/*,/Oracle Cloud ERP Data App/2 - Cloud Supply Chain/0. Procure2Pay overview
• Load Plan(s)
  • Input comma separated load plan names
  • e.g. LP_1,LP_2
• Dataflow(s)
  • Input comma separated dataflow names
  • e.g. TestAntiJoin,Alteryx_Forecast_LE_Forecast_Allocation

4. Group Access Control

Create assignment rules that will be applied on the selected assets. In the first column you need to enter Group Name. In the second column select suitable permissions for the group. The group should already exist. The script does not create the group.

Code

The app’s code is continuously updated as new features are added. Please contact our support team to obtain the latest build.

Screenshots

Screenshot - 1

Screenshot - 2

Screenshot - 3

Screenshot - 4

Screenshot - 5