Flags
In order to accommodate various migration scenarios, where entities need to be smoothly transitioned, we offer a powerful solution through custom Flags. These Flags enable you to apply specific logic to your migration process.
To utilize these Flags, simply include them in your command with the --flags option, like: --flags HELM_INFRA_WITH_STAGE_VAR.
Available Flags
Here's a detailed breakdown of the available Flags and their descriptions:
| Flag name | Default | Description |
|---|---|---|
HELM_INFRA_WITH_STAGE_VAR | True (0.3.10) | This helps with migrating Helm-based workflows. In the Next-Generation (NG) implementation, the release name has been relocated from the Helm step to the Infrastructure definition. To facilitate this, this flag introduces Stage variable autogenerated_release_name with value of FG Helm step's release name. This is referenced in Helm infrastructure definition with value <+stage.variables.autogenerated_release_name>. |
SEQUENTIAL_CREATION | False | If the migrated pipelines have replaced static inputs with runtime inputs, this flag would help |
LONG_RELEASE_NAME | False | Default release names for Kubernetes deployments are migrated with short generate release name <+INFRA_KEY_SHORT_ID>. If required, you can enable this flag to use long generated release names <+INFRA_KEY> |
ENV_AT_DIFFERENT_LEVEL | False | Enable this will allow environment creation at different level.(Default is at project level) |
PREFER_SERVICE_VARIABLE_OVERRIDES | False | Enable this when <+serviceVariableOverrides.var> is prefered over <+serviceVariables.var> |
SCRIPT_TO_FILE_STORE | False | When enabled, every script content is stored in the Harness file store instead of inline inside the step. |