Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

YAML entities don't populate mapped Marathon ports #254

Open
johnmccabe opened this issue Mar 24, 2016 · 1 comment
Open

YAML entities don't populate mapped Marathon ports #254

johnmccabe opened this issue Mar 24, 2016 · 1 comment

Comments

@johnmccabe
Copy link
Member

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
Copy link
Member

grkvlt commented Apr 25, 2016

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants