Why did you use paramaters here and not just add onto variables? Usually I think of parameters in a top level YML as items we pass during manually queueing. This pipeline isn't manually queued that I'm aware of though.

I don't believe you can have object types variables - using parameters allows me to just pass around a single pool parameter, instead of having different sets of variables to set different fields in the pool (like we had to do before).

See https://learn.microsoft.com/en-us/azure/devops/pipelines/process/variables?view=azure-devops&tabs=yaml%2Cbatch

All variables are strings and are mutable.

Indeed it is only parameters that can have complex data structures like objects. YAML always amazes me.

Note: variables can be marked as non-mutable now

variables: 
- name: key
   value: value
   readonly: true

this is the part where using a single pool parameter is much nicer. Don't need conditional definitions here and 3 separate arguments.

Indeed it is only parameters that can have complex data structures like objects. YAML always amazes me.

Note: variables can be marked as non-mutable now

variables: 
- name: key
   value: value
   readonly: true