autowakeup application should be excluded from auto-enrollment

[pradyutsarma]

[Running on code from the develop branch] I create a service instance of autosleep and the instance ignores the autosleep application (of course) but binds to the autowake application. Shouldn't the autowake application also be by default, neglected by the autosleep app?

Thanks and Regards, Pradyut.

[gberche-orange]

thanks @pradyutsarma for this feedback and suggestion.

Indeed the current self exclusion from enrollment should be extended to the autowakeup app.

As a short term workaround, I'll enhance the documentation to suggest to deploy autosleep and autowake up in a distinct separate space from enrolled spaces.

[arnaudruffin]

Oops 😄 Another short term workaround could be to use the exclude-from-auto-enrollment parameter to filter the autowakeup app.

[arnaudruffin]

Hi everyone

We had a look at this issue and we chose to implement the following mechanism in next release:

The SpaceEnroller worker (in charge of automatically binding the applications to autosleep) will automatically filter out the applications that are map to a route with a host equals to "*" (using CF java client). This means having to retrieve all routes for all application during our scans, but we think it's acceptable.

feel free to react. 😄

[arnaudruffin]

after an offline discussion with @gberche-orange, we decided it wouldn't be necessary, as this use case should never occure in production. We will keep using the exclude-from-auto-enrollment workaround in our acceptance tests