Fix usage of id() and super() methods in Docker apps

Change-Id: Ieb34aee28b796adfceebca0c825d05de02cf37ac
Closes-Bug: #1593682
(cherry picked from commit 1d0fc0a3e0)
This commit is contained in:
Tetiana Lashchova
2016-06-17 14:32:06 +03:00
committed by Sergey Kraynev
parent 60f52e4af5
commit 3b233af5cb
5 changed files with 6 additions and 6 deletions

View File

@@ -50,7 +50,7 @@ Methods:
deploy:
Body:
- $.influxDB.deploy()
- $.super($.deploy())
- super($, $.deploy())
getContainer:

View File

@@ -56,7 +56,7 @@ Methods:
publish => false,
redisMaster => $this.redisMaster)
- $.redisSlave.deploy()
- $.super($.deploy())
- super($, $.deploy())
getContainer:

View File

@@ -39,7 +39,7 @@ Methods:
deploy:
Body:
- $.mongodb.deploy()
- $.super($.deploy())
- super($, $.deploy())
getContainer:
Body:

View File

@@ -273,7 +273,7 @@ Methods:
- applicationName:
Contract: $.string().notNull()
Body:
- Return: format('{0}-{1}', $applicationName, $.id())
- Return: format('{0}-{1}', $applicationName, id($))
_removeApplicationEndpoints:
@@ -305,4 +305,4 @@ Methods:
getInternalScopeId:
Body:
Return: $.id()
Return: id($)

View File

@@ -311,7 +311,7 @@ Methods:
getInternalScopeId:
Body:
Return: $.kubernetesCluster.id()
Return: id($.kubernetesCluster)
scalePodDown:
Usage: Action