On DC/OS Enterprise, one can run with a strict security mode. In this environment, DC/OS schedulers cannot talk directly to Mesos masters on port 5050, but must rather go through DC/OS adminrouter. This requires 2 things not previously present in mesos-rxjava
HTTPS support (talking to adminrouter over https)
Ability to set an Authorization header
I did not do anything additionally to support enterprise other than the 2 items above. I took care of actually authenticating a service account and refreshing the token within my scheduler.
NOTE: I am aware that I need to add some tests and comments to make this PR complete. I wanted to at least get this out there for initial review as I know the project has changed ownership. I can follow any new guidance on formatting, docs, tests, etc.
DC/OS Enterprise Support
This is in support of #86
On DC/OS Enterprise, one can run with a strict security mode. In this environment, DC/OS schedulers cannot talk directly to Mesos masters on port 5050, but must rather go through DC/OS adminrouter. This requires 2 things not previously present in mesos-rxjava
I did not do anything additionally to support enterprise other than the 2 items above. I took care of actually authenticating a service account and refreshing the token within my scheduler.
NOTE: I am aware that I need to add some tests and comments to make this PR complete. I wanted to at least get this out there for initial review as I know the project has changed ownership. I can follow any new guidance on formatting, docs, tests, etc.
Thanks!