search

brooklyncentral / clocker

Apache Brooklyn cloud native infrastructure blueprints
Apache License 2.0
428 stars 66 forks source link

YAML entities don't populate mapped Marathon ports #254

Open johnmccabe opened 8 years ago

johnmccabe commented 8 years ago

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.

grkvlt commented 8 years ago

Probably same issue as #280 so a similar fix would work