This repository has been archived by the owner on Oct 23, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 841
Validation for app creation & update should not differ #1446
Milestone
Comments
That's a bug but there is a work around. You can omit the {
"container": {
"type": "DOCKER",
"docker": {
"image": "sloppy/apache-php",
"network": "BRIDGE",
"portMappings": [
{
"containerPort": 80,
"hostPort": 0,
"protocol": "tcp"
}
]
}
},
"id": "apache",
"instances": 1,
"cpus": 0.1,
"mem": 512
} Also notice that (See #1418 if you think that should be changed.) |
Note: Creating an app should have the same validation rule as updating an app. |
kolloch
changed the title
PUT fails in 0.8.1
Validation for app creation & update should not differ
May 18, 2015
The problem was actually not the validation itself but the serialization of cmd: "". An app without args and cmd: "" is automatically translated into an app with cmd: null and args: []. When you try to add a cmd to that, you see the validation error message above. I will solve it in two ways:
|
aquamatthias
added a commit
that referenced
this issue
May 22, 2015
Fixes #1446 - Disallow empty strings for app.cmd
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
starting an app with
then changing memory with PUT
fails with
The text was updated successfully, but these errors were encountered: