v0.1.9-beta - Workflow steps support details

With this release, the account & application summary will provide details of which workflow steps are supported, not supported & have to be manually migrated over to NG.
Sample result for workflow steps -

┌─────────────────────────────────────────────────────────────────────┐
│                             WORKFLOW (9)                            │
├─────────────────────────────────────────────────────────────────────┤
│                            Workflow Types                           │
├───────────────────────────────────┬────────────────┬────────────────┤
│ BASIC                             │ 1              │ SUPPORTED      │
│ BLUE_GREEN                        │ 1              │ SUPPORTED      │
│ BUILD                             │ 2              │ SUPPORTED      │
│ CANARY                            │ 2              │ SUPPORTED      │
│ MULTI_SERVICE                     │ 1              │ SUPPORTED      │
│ ROLLING                           │ 2              │ SUPPORTED      │
├───────────────────────────────────┴────────────────┴────────────────┤
│                                Steps                                │
├───────────────────────────────────┬────────────────┬────────────────┤
│ TERRAFORM_PROVISION               │ 1              │ MANUAL_EFFORT  │
│ JIRA_CREATE_UPDATE                │ 3              │ SUPPORTED      │
│ K8S_BLUE_GREEN_DEPLOY             │ 2              │ SUPPORTED      │
│ K8S_DEPLOYMENT_ROLLING            │ 3              │ SUPPORTED      │
│ KUBERNETES_SWAP_SERVICE_SELECTORS │ 1              │ SUPPORTED      │
│ RESOURCE_CONSTRAINT               │ 1              │ MANUAL_EFFORT  │
│ TERRAFORM_DESTROY                 │ 2              │ MANUAL_EFFORT  │
│ COMMAND                           │ 1              │ UNSUPPORTED    │
│ JENKINS                           │ 1              │ SUPPORTED      │
│ K8S_CANARY_DEPLOY                 │ 4              │ SUPPORTED      │
│ K8S_DELETE                        │ 4              │ SUPPORTED      │
│ APPROVAL                          │ 2              │ SUPPORTED      │
│ ARTIFACT_CHECK                    │ 1              │ IGNORE         │
│ HTTP                              │ 2              │ SUPPORTED      │
│ K8S_SCALE                         │ 1              │ SUPPORTED      │
│ SHELL_SCRIPT                      │ 13             │ SUPPORTED      │
│ TERRAFORM_APPLY                   │ 1              │ MANUAL_EFFORT  │
└───────────────────────────────────┴────────────────┴────────────────┘

v0.1.8-beta - Details for skipped entities

We now log entities that got skipped and possible reason of why they got skipped.
Here is a sample log -

INFO[2023-02-09T19:07:51+05:30] Here are the details of entities that got skipped while migrating -
WARN[2023-02-09T19:07:51+05:30] Unsupported/Unrecognized connector in NG      appId= id=PmpWLMKfT_mYDjleCuw-cw name=PHYSICAL_DATA_CENTER type=CONNECTOR
WARN[2023-02-09T19:07:51+05:30] Unsupported/Unrecognized connector in NG      appId= id=ppgO2lDlS025z2y9npci8A name=HELM_GCS_CONNECTOR type=CONNECTOR
WARN[2023-02-09T19:07:51+05:30] Unsupported/Unrecognized connector in NG      appId= id=IRq_0B97RPiu9LNoGdjp4g name="HELM S3" type=CONNECTOR

This will log in case there were connectors, services, workflows & pipelines that got skipped due to any reason.

v0.1.7: Support migrating workflows & pipelines with app command

The app command can now be used to migrate all workflows & pipelines in an application. Use the --all flag with the app command. If you were using the workflows & pipelines commands earlier to migrate all workflows & pipelines, then you can use the app command to achieve the same result.

Avoid using the --all flag if you wish to migrate specific workflows or pipelines.

Example:

harness-upgrade --load templates/app.yaml app --all

v0.1.6 - Async Support & Expressions CLI tool

With this release -

1. We now use async APIs to migrate all entities. This ensures we do not face any timeout issues during the upgrade process.
2. Expressions CLI support. The tool can now replace all known expressions from CG with equivalent NG expressions. It also lets you know which expressions cannot be migrated automatically, so you can manually do a find & replace in such scenarios.
3. Github release check now prints the release URL & also suggests pre-release if you are currently using a pre-release version of the CLI.

v0.1.5-beta Upgrade is now async instead of Sync

With this release, the API used to migrate account-level entities, apps, workflows & pipelines now uses async APIs instead of sync.

v0.1.4-beta: Support replacement of expressions from local file store

Support replacement of expressions from current & subdirectories. By default, only processes json, yaml & yml file extensions.

v0.1.3-beta: Support for Creating projects in bulk

We now support creating a project per app in the account. We then create a corresponding FILE.yaml with migration data such as apiKey, account, scopes, etc.

v0.1.2 Support for providing full urls for cg & ng.

Support for providing -
--source-app and --destination-project as CLI flags instead of providing accountId, appId, orgId& projectId in the input.

In case of a non-200 response code, we log the errors.

Fix the formatting of the data shown in table

Fix the formatting of the data shown in table

v0.1.0: Ability to check for harness-upgrade updates

With this update, we now check if a new release of this tool is available. If a release is available we let the user know of the new version available.