Getting Started
This guide shows a practical first setup for iFlowKit CLI.
0. Build and run
From the repository root:
go build ./cmd/iflowkitThis creates a local binary, usually named iflowkit.
1. Show local paths
Use where to see local configuration paths and current profile context:
iflowkit whereConfiguration root is based on os.UserConfigDir():
{user-config-dir}/iflowkit2. Initialize developer config
iflowkit config init
iflowkit config showDeveloper config stores CLI preferences that are not specific to a customer profile.
3. Create and select a profile
iflowkit profile init
iflowkit profile list
iflowkit profile use --id {profileId}
iflowkit profile currentA profile represents a customer or working context. Tenant service keys are stored under profiles.
4. Add tenant service keys
Import from JSON
iflowkit tenant import --file service-key-dev.json --env dev
iflowkit tenant import --file service-key-qas.json --env qas
iflowkit tenant import --file service-key-prd.json --env prdSet fields directly
iflowkit tenant set --env dev \
--url https://{cpi-host}/ \
--token-url https://{oauth-host}/oauth/token \
--client-id {id} \
--client-secret {secret}5. Configure Git provider token
Sync workflows may create or push Git repositories. Use environment variables for tokens.
Preferred:
export IFLOWKIT_GIT_TOKEN={token}Supported fallbacks:
export GITHUB_TOKEN={token}
export GH_TOKEN={token}
export GITLAB_TOKEN={token}
export GITLAB_PRIVATE_TOKEN={token}6. Initialize a sync repository from DEV
iflowkit sync init --id {packageId}
cd {packageId}This exports the DEV tenant IntegrationPackage into a Git repository and initializes .iflowkit metadata.
7. Daily sync workflows
Git → CPI
iflowkit sync pushCPI → Git
iflowkit sync pullCompare with an environment branch
iflowkit sync compare --to qas
iflowkit sync compare --to prdPromote between environments
iflowkit sync deliver --to qas
iflowkit sync deliver --to prdPRD operations require explicit --to prd.
Inspect deployment records
iflowkit sync deploy status --env dev8. Logs
The CLI writes logs under:
{user-config-dir}/iflowkit/logs/YYYY-MM-DD.logFor more detail during troubleshooting:
iflowkit --log-level debug sync push