trasloco

Chef@1 is retired: migrate off its platform or external tool

The short answer

Retirement date
Removal date
. Pipelines that still use it fail after removal.
Replacement
No replacement task.
Kind of migration
retired platform or external tool: no drop-in replacement
Automatic rewrite
No. This task needs a manual migration. trasloco modernize --check still finds the step.
Recommended action
Use a supported Chef extension or invoke the current Chef CLI from a script step.

Official sources

Last verified:

Why does my pipeline show a retirement error for Chef@1?

On , Azure Pipelines shows a retirement error for Chef@1, but the run does not fail. On , pipelines that still use Chef@1 fail.

Find it in your pipelines

With trasloco:

trasloco modernize --check

Install trasloco from the latest release.

With plain grep, nothing to install:

grep -rniwF 'Chef@1' --include='*.yml' --include='*.yaml' .

How to migrate

Use a supported Chef extension or invoke the current Chef CLI from a script step.

Chef@1 retirement FAQ

Is Chef@1 deprecated?

Yes. Chef@1 is retired on 2026-10-15. Azure Pipelines shows a retirement error, but the run does not fail until removal.

When does Chef@1 stop working?

Chef@1 is removed on 2027-03-15. Pipelines that still use it fail after removal.

What should I use instead of Chef@1?

There is no drop-in replacement task for Chef@1. Use a supported Chef extension or invoke the current Chef CLI from a script step.