removed classifier_synchronization_period override

[MartyEwings]

r10k postrun command is not called when using code manager disabling classifier scheduled sync results in the classifier never syncing automatically

[npwalker]

@MartyEwings what version of PE? It definitely used to work and I thought that file sync now updated the classifier for the user?

[MartyEwings]

I was using 2017.3, and the customer on the LTS

[MartyEwings]

Think post environment hooks are how ur supposed to do this now

https://puppet.com/docs/pe/2016.4/code_mgr_custom.html#postenvironmenthooks

[npwalker]

@MartyEwings ah yea, so I've always disabled classifier sync and just told users to hit the refresh button in the console because even when you use the background sync it doesn't refresh for a web page that's already open.

However, I can get onboard with using the default and not disabling it at this point. I'd prefer we just remove those 4 lines altogether instead of commenting out though.

[MartyEwings]

@npwalker Ok will do, main problem with that isn’t the classes, but if you have a new environment, it does not appear in the drop down when creating a new environment group until refresh occurs, and the button is hidden in existing node groups

[npwalker]

@MartyEwings environments aren't refreshed in an open console web page either. That still requires a full page refresh or a refresh classes button push.

[MartyEwings]

@npwalker this wasn’t refreshing in my testing after restarts and code deploys, And full refreshes, basically didn’t seems to be any mechanism to auto refresh without pressing the button, if the auto refresh was disabled

[npwalker]

@MartyEwings yes if the classifier sync is off then the only way is to push the refresh classes button.

If classifier sync is on then you have a new option. Wait until the every 10 minute sync happens and then full page refresh.

I don't think that just be not disabling classifier sync causes environments to refresh outside of the 10 minute sync?