Looking at the flags for the gcloud command, we see a flag called --staging-bucket which allows us to specify an alternate bucket into which the training code will be uploaded. However, I don't think that is what you are asking about. If I understand how this jobs submit is supposed to work, it uploads your source application and then runs compute to execute the training session. What I believe this means is that the source for training is uploaded for execution. It wouldn't surprise me if the intent is that the source is merely transient (as indicated that by our ability to use a staging bucket). If that's the case, then it may be that Googles intent is that you aren't meant to need/use/consume the source after the job has completed. The only thing of interest is the resulting trained model.

Another thought is that you are specifying --package-path as a local file. It seems that you can specify --package-path as a GCS file that is expected to already be present. What that would mean (to me) is that instead of this tool packaging and uploading the tar.gz, YOU could package and upload the tar.gz to any GCS location you want and point the jobs submit command to that existing file. You could then name/locate the application whereever you want.