Soft deprecate azure-resource-provider-folder and remove from feeds

[timotheeguerin]

Right now this just document as deprecated but doesn't flag a warning as we are still deciding if we should fix v1 spec or wait until they are migrated.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/Azure/typespec-azure/@azure-tools/typespec-autorest@3836

npm i https://pkg.pr.new/Azure/typespec-azure/@azure-tools/typespec-autorest-canonical@3836

commit: cdb3b8c

[azure-sdk]

All changed packages have been documented.

• ✅ @azure-tools/typespec-autorest-canonical
• ✅ @azure-tools/typespec-autorest

Show changes

@azure-tools/typespec-autorest - deprecation ✏️

Deprecate azure-resource-provider-folder option.,> ,> diff lang=yaml,> -azure-resource-provider-folder: "resource-manager",> -output-file: "{azure-resource-provider-folder}/{service-name}/{version-status}/{version}/openapi.json",> +output-file: "resource-manager/{service-name}/{version-status}/{version}/openapi.json",>

@azure-tools/typespec-autorest-canonical - deprecation ✏️

Deprecate azure-resource-provider-folder option.,> ,> diff lang=yaml,> -azure-resource-provider-folder: "resource-manager",> -output-file: "{azure-resource-provider-folder}/{service-name}/{version-status}/{version}/openapi.json",> +output-file: "resource-manager/{service-name}/{version-status}/{version}/openapi.json",>

[azure-sdk]

You can try these changes here

🛝 Playground	🌐 Website

[mikeharder]

is this safe, since version is only set on L356, if azureResourceProviderFolder is set?

[timotheeguerin]

I think it didn't actually matter because the version is always set as the parameter when it matters. This is only in the case where it was set via the openapi3 @info decorator which should never happen.
But yeah good to remove the condition.