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
Deploying a Java based entity currently behaves as expected with mapped marathon port sensors being populated correctly, for example deploying an org.apache.brooklyn.entity.database.postgresql.PostgreSqlNode entity sees a mapped.postgresql.port populated with the port exposed by Marathon.
If I deploy a Yaml based entity however the mapped ports mapped.docker.port.XXXX do get created but are never populated (the entity deploys successfully and is accessible via the mapped port but you have to get at it via the Marathon UI), I've attached a sample blueprint that demonstrates the issue mapped_port_yaml_problem.txt.
The text was updated successfully, but these errors were encountered:
Deploying a Java based entity currently behaves as expected with mapped marathon port sensors being populated correctly, for example deploying an
org.apache.brooklyn.entity.database.postgresql.PostgreSqlNode
entity sees amapped.postgresql.port
populated with the port exposed by Marathon.If I deploy a Yaml based entity however the mapped ports
mapped.docker.port.XXXX
do get created but are never populated (the entity deploys successfully and is accessible via the mapped port but you have to get at it via the Marathon UI), I've attached a sample blueprint that demonstrates the issuemapped_port_yaml_problem.txt.
The text was updated successfully, but these errors were encountered: