Migrating from Chef Infra Client 18 to Chef Infra Client 19 is more than a simple version upgrade. With the transition from Omnibus to Habitat based packaging, a newer Ruby version, changes to installation paths, updated licensing requirements, the migration requires careful planning and compatibility checks. In this blog, we will explore the step by step approach to migrating safely using azure DevOps pipeline.
Prerequisites:
- Windows servers: The target Windows servers must have Chef Infra Client installed.
- Azure DevOps Deployment Group: Each target server must be registered with the appropriate Azure DevOps Deployment Group.
- Valid Chef License Key: Ensure a valid Chef License Key is available for downloading and installing Chef Infra Client 19.
- Chef Migration Tools: Ensure the required Chef migration tools, including migrate-ice, are available and configured.
