v0.2.9-beta - Support for migrating specific entities by name & id

What's Changed

• Support cross-account upgrade
• Support for Self Managed Platform upgrade
• Support importing individual entities by either names or id for
  • Services
  • Environments
  • Secrets
  • Connectors

v0.2.8 - Creation of Projects using CSV

What's Changed

• We now support the creation of projects using CSV. This allows for much more control over where the projects will be created. It allows customisation of the project's name, identifier & org.
• Support for creation & deletion of org. You can now create an org directly from the CLI & delete one or more organisations by name or identifier.

v0.2.7 Support migration of services

With this release, we can migrate all services from an application.

harness-upgrade --load FILE service

The above will migrate all the services from an application. It will migrate all the associated manifests, secrets & connectors.

v0.2.6 - Summary of expressions that were not migrated

What's Changed

As part of the summary, we now list details of entities whose expressions have not been migrated correctly. We list the details such as org, project & identifiers of the entities in NextGen, along with their expressions that were not converted.

Sample table

┌────────────┬──────────────────────┬─────────┬─────────┬─────────────────────┐
│ TYPE       │ IDENTIFIER           │ ORG     │ PROJECT │ EXPRESSIONS         │
├────────────┼──────────────────────┼─────────┼─────────┼─────────────────────┤
│ FILE_STORE │ helloWorldValuesYaml │ default │ demo    │ artifact.source.pqr │
│            │                      │         │         │ artifact.source.xyz │
└────────────┴──────────────────────┴─────────┴─────────┴─────────────────────┘

v0.2.5 User groups migration

What's Changed

Support for user groups migration

You can now migrate user groups using the following command -

harness-upgrade --load FILE user-groups

User groups will be migrated to the account scope.

Support to auto-update CLI

You can now auto-update the CLI using the following command -

harness-upgrade update

v0.2.4 - Support to customise identifier casing

You can now control how Harness generates the identifiers for the entities. Previously we used the names & converted them to camelCase format. We have now added support for lowercase identifier format.

harness-upgrade  --identifier-format LOWER_CASE --load FILE app

Just so you know, this affects all entities that Harness creates. If you have already migrated entities previously, they would have been migrated to camelCase. Please clean them up from your projects & account and rerun the Upgrade. If you do not do this, you might find multiple entities referencing the same First Gen entity, one in camelCase and the other in smallcase.

v0.2.3-beta - Support to remove Projects

What's Changed

Support deletion of projects by names & identifiers
You can now use the CLI to remove multiple projects by name or identifiers.

To remove by name

harness-upgrade project --names projectName1,projectName2 rm

To remove by identifiers

harness-upgrade project --identifiers identifier1,identifier2 rm

v0.2.2 - Workflows as Pipelines & expressions improvement

What's Changed

Support for creating pipelines from workflows

Previously we created workflows as stage templates & if we wanted pipelines in NG to execute these workflows, it required manual effort. We can now use this command to create pipelines.

harness-upgrade workflows --as-pipelines 

I'd like to point out that workflows will continue to be created as stage templates.

Support secret scope & convert secret to camel case

Secrets referenced in remote manifests work similarly to the migration. FirstGen secrets referenced are converted to camel case & we attach the scope passed using the --secret-scope flag.

harness-upgrade --secret-scope org expressions --dry-run

v0.2.1 - Support for overriding expressions

With this new release, you can now provide custom expressions from a file to assist in making the first-generation remote manifest files compatible with the next-gen.

You can use this functionality to override the Harness-recommended expressions to anything you choose.

appName: <+project.name>
app.name: <+org.name>

Here is how to use this -

harness-upgrade expressions --dry-run --override /path/to/override.yaml

v0.2.0 - Include support status for entities

With this release, we now show the auto migration support status for workflows, services & connectors. This is to help understand the level of automatic migration that is capable and to identify the possible areas that require manual effort to complete the migration.