P1 - Job config is modified after it is imported/uploaded/cloned

[yqwang-ms]

Organization Name:

Short summary about the issue/question:

Import from Submit Job page:
Left original, right after import

Import from Submit Job by plugin page:
Left original, right after import

User will confuse why just import/upload/clone will change his job config, and concerns if it can also reproduce this job anymore.
Suggest:

1. The defaulting should only be done after submission phase.
2. And we should not change user already specified values in any phase.

We should always pay attention to our reproducibility.

Brief what process you are following:

How to reproduce it:

OpenPAI Environment:

• OpenPAI version:
• Cloud provider or hardware configuration:
• OS (e.g. from /etc/os-release):
• Kernel (e.g. uname -a):
• Hardware (e.g. core number, memory size, storage size, GPU type etc.):
• Others:

Anything else we need to know:

[yqwang-ms]

temp workaround: using sdk or cli to submit raw job config yaml

[Binyang2014]

After #4016 is merged, we will keep the Yaml contents are equivalent. But may change the order of config sentences.
As discussed, it's acceptable. Close this issue.

[yqwang-ms]

Acceptable in current does not mean we totally solved this. Defaulting should not be done at this phase.

[fanyangCS]

we need a better yaml editor

[scarlett2018]

• The defaulting should only be done after submission phase.
  the current validation updated the fields that is empty with default values, should not change users original form.
• And we should not change user already specified values in any phase.