You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 7b3617e
Browse filesBrowse the repository at this point in the historyBrowse files
fix(deploy): pass gcloud arguments as an array instead of a joined string (#3726)
spawnAsync built each gcloud command as one string and split it on
whitespace before calling spawn(), so any deploy option containing a
space was chopped into extra argv entries and a value from angular.json
could add flags of its own. It now takes command and args separately and
the three call sites pass arrays, removing the join and split entirely.
The close handler also rejected only on exit code 1, so a gcloud failure
with any other code, or a process killed by a signal, resolved as success
and a failed deploy reported as done. It now rejects on any non-zero or
null code.
The Cloud Run argument construction moved into two exported functions so
tests can assert the argv shape without mocking spawn, and functionName
and region gained schema patterns, since both also reach the generated
Cloud Functions source.
(cherry picked from commit 778625a)
Copy file name to clipboardExpand all lines: src/schematics/deploy/schema.json
+4-2Lines changed: 4 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -51,7 +51,8 @@
51
51
},
52
52
"functionName": {
53
53
"type": "string",
54
-
"description": "The name of the Cloud Function or Cloud Run serviceId to deploy SSR to"
54
+
"pattern": "^[A-Za-z][A-Za-z0-9_-]{0,62}$",
55
+
"description": "The name of the Cloud Function or Cloud Run serviceId to deploy SSR to. Must start with a letter and contain only letters, numbers, hyphens and underscores; on the Cloud Functions path this value also becomes a JavaScript identifier, so use only letters and numbers there."
0 commit comments