Scaling config yaml

[MPCherry]

Allow submitting a scaling config name alongside pipeline create.

[rossgray]

The only question I have is whether scaling_config represents a scaling config ID or name? If it's just one or the other, maybe it's worth naming it scaling_config_id or scaling_config_name so that it's obvious to people adding it to their YAML? Or if we're gonna support both then should be fine to leave as is

[MPCherry]

The only question I have is whether scaling_config represents a scaling config ID or name? If it's just one or the other, maybe it's worth naming it scaling_config_id or scaling_config_name so that it's obvious to people adding it to their YAML? Or if we're gonna support both then should be fine to leave as is

Its a name, I've copied the convention we used in the pipeline patch, but agree its slightly confusing.

[rossgray]

The only question I have is whether scaling_config represents a scaling config ID or name? If it's just one or the other, maybe it's worth naming it scaling_config_id or scaling_config_name so that it's obvious to people adding it to their YAML? Or if we're gonna support both then should be fine to leave as is

Its a name, I've copied the convention we used in the pipeline patch, but agree its slightly confusing.

ok, I guess we'll have to document this somewhere anyway, so we can make sure we specify that it needs to be the name and not the ID

[MPCherry]

The only question I have is whether scaling_config represents a scaling config ID or name? If it's just one or the other, maybe it's worth naming it scaling_config_id or scaling_config_name so that it's obvious to people adding it to their YAML? Or if we're gonna support both then should be fine to leave as is

Its a name, I've copied the convention we used in the pipeline patch, but agree its slightly confusing.

ok, I guess we'll have to document this somewhere anyway, so we can make sure we specify that it needs to be the name and not the ID

Just changed it anyway lol, for the api calls and models themselves we can stick to this convention but the config having name just makes it clearer.

[rossgray]

nice!