test all service crates in parallel

[cataggar]

This makes it possible to check all the services in parallel jobs. The workflow definitions can be generated when the services are updated.

[ctaggart]

I was hoping it would publish 1 job at a time. Looks like it is doing 20 concurrently. :/

https://docs.github.com/en/actions/learn-github-actions/usage-limits-billing-and-administration

[cataggar]

crates.io had to problem with the concurrent crate updates. The backoff appears that it was just for new crates. docs.rs put the azure_mgmt crates in a "priority: -1, so they get processed when capacity is available. It may take a few days. https://docs.rs/releases/queue

[bmc-msft]

Given these have access to CARG_REGISTRY_TOKEN, this should probably include documentation as to who has access to run these and what the process is to enable giving someone access to run these.

[cataggar]

Given these have access to CARG_REGISTRY_TOKEN, this should probably include documentation as to who has access to run these and what the process is to enable giving someone access to run these.

The publish actions are intended for running in your own fork where only you have access to run the actions. Do not add the CARGO_REGISTRY_TOKEN to the main repository. Only add it to your repository.

How is that ^^^?

[bmc-msft]

Discussion moved to the internal Teams instance for Azure SDK For Rust.