package

Work with IICS export package files locally. No authentication or API calls are required - all operations are performed on the local file system.

Synopsis

iics package <subcommand> [flags]

Subcommands

Subcommand	Description
`expand`	Extract an IICS export ZIP package to a directory
`create`	Assemble a new IICS export ZIP package from a directory
`dependencies`	Resolve and list transitive dependencies of an export package

package expand

Extracts the contents of an IICS export ZIP package to a target directory. JSON files are pretty-printed (2-space indent) to produce clean diffs in version control. Nested ZIP files (e.g. m_Test_Git.DTEMPLATE.zip) can be recursively expanded into directories.

The typical workflow for version-controlling IICS assets is:

iics export run - export assets to a ZIP package
iics package expand - extract the package to a versioned directory
Commit the directory to git
iics package create - reassemble the ZIP from the directory
iics import run - import the package to a target org

Flags

Flag	Short	Type	Required	Default	Description
`--file`	`-f`	string	yes		Path to the source ZIP package
`--target`	`-t`	string	yes		Destination directory; created if absent
`--recursive`	`-r`	bool		false	Recursively expand nested ZIPs into `<name>.zip/` directories
`--clean`	`-c`	bool		false	Delete target contents before expanding
`--yes`	`-y`	bool		false	Suppress the `--clean` confirmation prompt

All global flags apply.

Behavior details

Target directory

Created automatically with os.MkdirAll if it does not exist.
If the target contains files and --clean is not set, the command returns an error. This is intentional: in CI/CD pipelines the source directory should be empty so that deleted or renamed assets are detected by git status.
With --clean, the command counts and removes existing contents, prompting for confirmation unless --yes is also given.

JSON pretty-printing

All .json files are reformatted with 2-space indentation on extraction. This produces readable, diff-friendly output in git. It also means the SHA-256 hashes stored in exportPackage.chksum will differ from the originals; package create always regenerates the checksum from current file contents.

Recursive expand (--recursive)

Nested ZIP files (e.g. Mappings/m_Test_Git.DTEMPLATE.zip) are expanded into a directory with the same name including the .zip extension (e.g. Mappings/m_Test_Git.DTEMPLATE.zip/). The source zip file is not written to disk. When package create encounters a directory whose name ends in .zip, it re-packs it into a nested ZIP automatically.

Verbose output (--verbose)

Lists the ZIP entries before extraction and lists the target directory contents after.

Examples

# Basic expand
iics package expand \
  --file exports/my-project.zip \
  --target src/iics

# Expand and overwrite an existing directory (with confirmation)
iics package expand \
  --file exports/my-project.zip \
  --target src/iics \
  --clean

# Non-interactive expand (CI/CD)
iics package expand \
  --file exports/my-project.zip \
  --target src/iics \
  --clean --yes

# Recursively expand all nested ZIPs (e.g. DTEMPLATE, MTT assets)
iics package expand \
  --file exports/my-project.zip \
  --target src/iics \
  --recursive --verbose

# Basic expand
iics package expand `
  --file exports/my-project.zip `
  --target src/iics

# Expand and overwrite an existing directory (with confirmation)
iics package expand `
  --file exports/my-project.zip `
  --target src/iics `
  --clean

# Non-interactive expand (CI/CD)
iics package expand `
  --file exports/my-project.zip `
  --target src/iics `
  --clean --yes

# Recursively expand all nested ZIPs (e.g. DTEMPLATE, MTT assets)
iics package expand `
  --file exports/my-project.zip `
  --target src/iics `
  --recursive --verbose

package create

Assembles a new IICS export ZIP package from the contents of a source directory and regenerates exportPackage.chksum to match. The resulting ZIP is suitable for import via iics import run.

Selective packaging is supported with --manifest-file or piped stdin. When a manifest is supplied, only matching assets are included, exportMetadata.v2.json is regenerated for selected assets, and ContentsofExportPackage_<name>.csv is generated. The regenerated metadata keeps source org fields from the source workspace metadata and sets the metadata name to --name or the target ZIP basename.

Dot files (names starting with .) and any existing exportPackage.chksum are excluded. Directories whose name ends in .zip (produced by package expand --recursive) are re-packed into nested ZIP entries automatically.

Flags

Flag	Short	Type	Required	Default	Description
`--source`	`-s`	string	yes		Source directory to package
`--target`	`-t`	string	yes		Output ZIP file path
`--force`	`-f`	bool		false	Overwrite existing output file
`--manifest-file`	`-m`	string			Inclusion manifest file (`.txt`, `.csv`, `.json`, `.yaml`); omit to read stdin
`--name`	`-n`	string			Package name used for generated `ContentsofExportPackage_<name>.csv` file
`--include-tags`		bool		false	Include root `tags` in regenerated `exportMetadata.v2.json`
`--exclude-found-transitive`		bool		false	Exclude rows where `DEPENDENCY=transitive` and selected `STATUS (<target>)=found`
`--status-target`		string			Target key for `STATUS (<target>)` column (for example `qa`)

All global flags apply.

Checksum file

exportPackage.chksum is always regenerated from the actual files in the source directory. The format matches the Informatica CLI v2 package format:

One path=SHA256 entry per file, sorted alphabetically
Spaces in paths escaped as \ followed by a space
SHA-256 hash in uppercase hex
No header or timestamp line

Selective manifest input

Manifest rows may reference assets by ID, location, or path and type. Supported formats are the same as export artifact parsing: txt, csv, json, and yaml.

--manifest-file reads from a file.
If --manifest-file is omitted and stdin is piped, stdin is auto-detected and used.
If neither is provided, package create keeps existing full-source behavior.

Target-aware transitive exclusion:

Enable with --exclude-found-transitive.
The manifest must be CSV with DEPENDENCY and STATUS (<target>) columns.
Use --status-target when multiple status columns exist (for example STATUS (qa), STATUS (stg)).
Rows where DEPENDENCY=transitive and STATUS (<target>)=found are excluded.
Verbose exclusion count includes:
- manifest rows excluded directly by DEPENDENCY=transitive and STATUS (<target>)=found
- additional transitive found dependencies that would only be included through in-package closure expansion (suppressed when --exclude-found-transitive is enabled)
Parent Project and Folder container objects inferred from selected asset paths are included so first-time target deployments can create container structure metadata.
For selective packaging without --exclude-found-transitive, package-internal referenced dependencies are re-included to preserve dependency closure.
With --exclude-found-transitive, package file content excludes filtered transitive assets, but exportMetadata.v2.json keeps the full source dependency graph to preserve CDI import semantics.
Use --include-tags to carry root tags from source metadata into regenerated selective package metadata.

Verbose output (`--verbose`)

Prints the list of files added to the ZIP before the summary line.

Examples

# Basic create
iics package create \
  --source src/iics \
  --target dist/my-project-reimported.zip

# Overwrite existing output
iics package create \
  --source src/iics \
  --target dist/my-project.zip \
  --force --verbose

# Build a selective package from a manifest file
iics package create \
  --source src/iics \
  --target dist/my-project-selective.zip \
  --manifest-file target/iics/import/conf/package_manifest.csv \
  --include-tags \
  --name my-project-selective \
  --force

# Exclude transitive dependencies already found in target QA
iics package create \
  --source src/iics \
  --target dist/my-project-qa.zip \
  --manifest-file testdata/package/create/build_package_qa.csv \
  --exclude-found-transitive \
  --status-target qa \
  --force

# Build a selective package from piped stdin
iics objects dependencies --file dist/export.zip --output csv \
  | iics package create --source src/iics --target dist/from-stdin.zip --force

# Basic create
iics package create `
  --source src/iics `
  --target dist/my-project-reimported.zip

# Overwrite existing output
iics package create `
  --source src/iics `
  --target dist/my-project.zip `
  --force --verbose

Round-trip workflow

# 1. Export from source org
iics export run \
  --artifacts-file objects.txt \
  --export-file-path dist/export.zip \
  --profile dev

# 2. Expand to versioned directory
iics package expand \
  --file dist/export.zip \
  --target src/iics \
  --clean --yes

# 3. Commit to git
git add src/iics
git commit -m "Update IICS assets"

# 4. Reassemble package from versioned sources
iics package create \
  --source src/iics \
  --target dist/import.zip \
  --force

# 5. Import to target org
iics import run \
  --zip-file dist/import.zip \
  --profile prod

# 1. Export from source org
iics export run `
  --artifacts-file objects.txt `
  --export-file-path dist/export.zip `
  --profile dev

# 2. Expand to versioned directory
iics package expand `
  --file dist/export.zip `
  --target src/iics `
  --clean --yes

# 3. Commit to git
git add src/iics
git commit -m "Update IICS assets"

# 4. Reassemble package from versioned sources
iics package create `
  --source src/iics `
  --target dist/import.zip `
  --force

# 5. Import to target org
iics import run `
  --zip-file dist/import.zip `
  --profile prod

Package file format

An IICS export package is a ZIP archive with the following structure:

<package-name>.zip
├── exportMetadata.v2.json        # Asset metadata with GUIDs, objectRefs, repoHandles
├── exportPackage.chksum          # SHA-256 checksums for all files
├── ContentsofExportPackage_*.csv # Asset inventory (present in server exports)
├── Explore/
│   └── <Project>/
│       ├── <Project>.Project.json
│       ├── <Folder>.Folder.json
│       └── <Folder>/
│           └── <Asset>.<TYPE>.xml  # or .zip for binary asset types
└── SYS/                          # Present when exported with dependencies
    └── <Connection>.<TYPE>.zip

Key files:

exportMetadata.v2.json - mandatory for import; contains per-asset metadata including repoInfo.repoHandle and objectRefs arrays
exportPackage.chksum - always regenerated by package create; IICS validates this on import

package dependencies

Resolves and lists transitive dependencies of every object in an IICS export package. The data source is exportMetadata.v2.json inside the package. No authentication is required for package-only analysis; a source org profile is used when available to resolve external GUIDs (assets referenced but not included in the package). Traversal continues recursively until no new dependency assets are discovered.

dependency=explicit is based on object definition files present in exportPackage.chksum (physically packaged assets). Metadata-only references that do not have backing object files in checksum are reported as dependency=transitive.

The command operates in two modes:

Default mode (no --publish): lists ALL dependencies regardless of type, including Folder, Project, Connection, AgentGroup, MTT assets, and more. Useful for auditing the full dependency graph. --target-profile is optional; when provided, each dependency is validated against the target org and missing assets are flagged. Output is sorted by path.

Publish mode (--publish): restricts output to publishable types only: AI_SERVICE_CONNECTOR, AI_CONNECTION, PROCESS, GUIDE, TASKFLOW. --target-profile or --report is required in this mode. Output is sorted by publish dependency order (primary) then path (secondary):

In publish mode, recursion still traverses through non-publishable intermediate assets so deeper publishable dependencies are included in the result.

Order	Type
1	`AI_SERVICE_CONNECTOR`
2	`AI_CONNECTION`
3	`PROCESS`
4	`GUIDE`
5	`TASKFLOW`

Use --order-by to override the default sort in either mode.

Flags

Flag	Short	Type	Required	Default	Description
`--file`	`-f`	string	yes*		Path to IICS export ZIP package
`--workspace`	`-w`	string	yes*		Path to expanded workspace directory
`--publish`		bool		false	Restrict to publishable types; requires `--target-profile` or `--report`
`--report`		string list			Compare dependencies across one or more target profiles (mutually exclusive with `--target-profile`)
`--target-profile`	`-t`	string			Profile name for single-profile target org validation (mutually exclusive with `--report`)
`--order-by`		string			Sort output by field: `path`, `type`, `status`, `warning`, `location`, `dependency`
`--exclude`	`-e`	string			Regex matched against `path.type` - excludes from BFS resolution
`--exclude-file`		string			Regex policy file; each matching `path.type` is excluded from BFS resolution
`--filter`		string			Regex matched against `location` (`(Explore
`--output-file`		string			Write output to a file
`--output-file-format`		string		`yaml`	Output file format: `table`, `json`, `csv`, `yaml`
`--output-file-fields`		string		`location,dependency,type,path,status,warning`	Comma-separated fields for output file rows

* --file and --workspace are mutually exclusive; exactly one is required.

When --order-by is provided it overrides the default sort (path-only or publish-priority). The secondary sort key is always path.

All global flags apply, including --output / -o.

Output columns

Each row includes a normalized location ((Explore|SYS)/path.type) and dependency marker. For package dependencies, dependency=explicit means the asset has a backing object file in exportPackage.chksum; dependency=transitive means it is reference-only in metadata or API-resolved during traversal.

Single-profile mode (no `--target-profile` or `--report`)

Column	JSON field	Description
`LOCATION`	`location`	Asset identifier as `(Explore
`DEPENDENCY`	`dependency`	`explicit` for checksum-backed package assets, `transitive` for metadata-only or API-resolved assets
`TYPE`	`type`	Asset type
`PATH`	`path`	Asset path without `Explore/` prefix

With `--target-profile <name>`

Column	JSON field	Description
`LOCATION`	`location`	Asset identifier as `(Explore
`DEPENDENCY`	`dependency`	`explicit` for checksum-backed package assets, `transitive` for metadata-only or API-resolved assets
`TYPE`	`type`	Asset type
`PATH`	`path`	Asset path without `Explore/` prefix
`STATUS (name)`	`status`	`found`, `missing`, or `unknown`; color-coded
`WARNING`	`warning`	Only shown when at least one warning exists

With `--report <profiles>`

Column	JSON field	Description
`LOCATION`	`location`	Asset identifier as `(Explore
`DEPENDENCY`	`dependency`	`explicit` for checksum-backed package assets, `transitive` for metadata-only or API-resolved assets
`STATUS (dev)`	`status_dev`	Per-profile status; color-coded
`STATUS (qa)`	`status_qa`	Per-profile status; color-coded
`WARNING (dev)`	`warning_dev`	CSV only - warning text per profile
`WARNING (qa)`	`warning_qa`	CSV only - warning text per profile

JSON and YAML output for --report uses a nested profiles map:

{
  "id": "Explore/MyProject/MyConn.AI_CONNECTION",
  "path": "MyProject/MyConn",
  "type": "AI_CONNECTION",
  "location": "Explore/MyProject/MyConn.AI_CONNECTION",
  "dependency": "explicit",
  "profiles": {
    "dev": { "status": "found" },
    "qa":  { "status": "missing", "warning": "asset not found in target org" }
  }
}

Output formats

Supports all standard formats via --output / -o: table, json, csv, yaml.

Additionally, -o mermaid renders the dependency graph as a Mermaid graph TD diagram (no extra Go dependencies - pure text generation). Missing assets (when --target-profile is set) are highlighted in red using a classDef missing style. Mermaid output is not supported with --report.

CI/CD environment variables

These environment variables override the target profile settings without modifying ~/.iics/config.yaml, which is useful in CI/CD pipelines. Applies to --target-profile only; --report uses named profiles from the config file.

Variable	Overrides
`IICS_TARGET_USERNAME`	target profile username
`IICS_TARGET_PASSWORD`	target profile password
`IICS_TARGET_REGION`	target profile region
`IICS_TARGET_LOGIN_URL`	target profile loginUrl

Examples

# Inspect full dependency graph from a ZIP file
iics package dependencies --file mypackage.zip

# Inspect from an expanded workspace
iics package dependencies --workspace ./src/iics

# Single-profile: validate publish deps and pipe to publish
iics package dependencies -f pkg.zip --publish --target-profile prod -o csv | iics publish run

# Single-profile: sort missing assets to the top
iics package dependencies -f pkg.zip --target-profile qa --order-by status

# Multi-profile: compare dev and qa side-by-side
iics package dependencies -f pkg.zip --report dev,qa

# Multi-profile: publish mode comparison across three orgs
iics package dependencies -f pkg.zip --publish --report dev,qa,prod

# Multi-profile: export comparison as JSON for downstream processing
iics package dependencies -f pkg.zip --report dev,qa -o json

# Multi-profile: export comparison as CSV for spreadsheet review
iics package dependencies -f pkg.zip --report dev,qa -o csv

# Exclude system connections, filter to a specific project
iics package dependencies -f pkg.zip --exclude '^SYS' --filter 'MyProject'

# Write dependency list to a JSON file with selected fields
iics package dependencies -f pkg.zip \
  --output-file deps.json \
  --output-file-format json \
  --output-file-fields location,dependency,type,status,warning

# Render dependency graph as Mermaid diagram
iics package dependencies -f pkg.zip -o mermaid

# Render publish-only graph with target validation for review
iics package dependencies -f pkg.zip --publish --target-profile prod -o mermaid

# Inspect full dependency graph from a ZIP file
iics package dependencies --file mypackage.zip

# Inspect from an expanded workspace
iics package dependencies --workspace ./src/iics

# Single-profile: validate publish deps and pipe to publish
iics package dependencies -f pkg.zip --publish --target-profile prod -o csv | iics publish run

# Multi-profile: compare dev and qa side-by-side
iics package dependencies -f pkg.zip --report dev,qa

# Multi-profile: publish mode comparison
iics package dependencies -f pkg.zip --publish --report dev,qa,prod

# Multi-profile: export as CSV for spreadsheet review
iics package dependencies -f pkg.zip --report dev,qa -o csv

# Render dependency graph as Mermaid diagram
iics package dependencies -f pkg.zip -o mermaid

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

package

Synopsis

Subcommands

package expand

Flags

Behavior details

Examples

package create

Flags

Checksum file

Selective manifest input

Verbose output (`--verbose`)

Examples

Round-trip workflow

Package file format

package dependencies

Flags

Output columns

Single-profile mode (no `--target-profile` or `--report`)

With `--target-profile <name>`

With `--report <profiles>`

Output formats

CI/CD environment variables

Examples

See also

FilesExpand file tree

package.md

Latest commit

History

package.md

File metadata and controls

package

Synopsis

Subcommands

package expand

Flags

Behavior details

Examples

package create

Flags

Checksum file

Selective manifest input

Verbose output (--verbose)

Examples

Round-trip workflow

Package file format

package dependencies

Flags

Output columns

Single-profile mode (no --target-profile or --report)

With --target-profile <name>

With --report <profiles>

Output formats

CI/CD environment variables

Examples

See also

Verbose output (`--verbose`)

Single-profile mode (no `--target-profile` or `--report`)

With `--target-profile <name>`

With `--report <profiles>`