Configurable Command Plugin Build Configuration

[MahdiBM]

Configurable Command Plugin Permissions changes are working very nicely and have resolved the other issue I had filed.

We should add build configuration to the list of configurable settings too, for heavier operations.

Example:

time swift package -c release --allow-writing-to-package-directory generate-code-from-openapi
...
________________________________________________________
Executed in   32.80 secs    fish           external
   usr time   49.43 secs    0.11 millis   49.43 secs
   sys time    0.81 secs    1.46 millis    0.80 secs

time swift package --allow-writing-to-package-directory generate-code-from-openapi
...
________________________________________________________
Executed in   68.68 secs    fish           external
   usr time  115.34 secs    0.12 millis  115.34 secs
   sys time    1.44 secs    1.74 millis    1.44 secs

The non-release version takes more than twice as much to finish, wasting ~36 seconds.

This is with hello-world-async-http-client-example and replacing openapi.yaml with GitHub's on my M1 Macbook Pro.

[award999]

The swift-plugin task type can take freeform args. Is there a strong justification to tie this to a setting?

[MahdiBM]

Hmm I'd say yes for this one? It should also be fine if you were to implement this in a more free-form way. Like accepting package-command-args. But it should be separate for each plugin as most plugins are not worth release-building.

[award999]

we can add a setting for default package command args similar to what is done for package resolve