IssueTracker

In order to create a vertex ai custom job while using gcloud commands from a default configuration, involves two operations:
1) a script for submitting jobs:
2) a config.yaml file that is used by the script above

Let’s assume that the customer specifies a directory, under the options:“baseoutputdirectory” or “outputUriPrefix”, such as:
“””
outputUriPrefix: gs://my-bucket/<experiment_name>/
“””

and wishes to submit two jobs, experiment1 and experiment2 which follow the same template, where the only difference between both configurations is the name of the job.

This simple change usually involves modifying both the script and the configuration, as such:
1) gcloud ai custom-jobs create \
--display-name experiment1 \
--region europe-west1 \
--config config.yaml

Because the --display-name flag needs to be changed. However this not enough, as there is still the need to specify the option where the directory is stated in the config.yaml file

The request is that both CLI and REST API versions contemplate the possibility to pass a name argument, for instance the argument for the “--display-name” to the config file, making this flow less prone to common mistakes.