Eugen

@bishopbm1 Could you please look at the PR, do you have any feedback or pointers on this change?

@shortdudey123 You mean it's better to leave it as is? Eg. configure everything at a run-time.

Yeah, adding `xenial` support after shipping StackStorm packages in `stable` packagecloud repo would be more consistent.

@docwhat Indeed. I think we’ll still support U14 for a while until stopping shipping deb packages after end of Trusty life. If you or someone wants to add Xenial support...

:+1: Just FYI it's a good thing to have, but not a big priority or something like that. Stating the obvious :)

A little bit more context. Per https://github.com/StackStorm/st2/pull/4891 note that `--always-copy` flag should be removed for both EL7 and EL8 as it breaks virtualenv for pack install in these systems. However...

My vision is that or we use it everywhere as possible, or not use at all. Something in between is less acceptable. Thereby, tagging it as `refactor`.

Also, we should be really careful here when considering migration, see [this comment](https://blog.chef.io/2014/01/23/attributes-or-data-bags-what-should-i-use/#comment-1213702855) by [Seth Vargo](https://github.com/sethvargo): > I'd also like to suggest/plea. Please don't force the use of a data...

Here is related feature request about enabling/disabling specific pack content (incl. `aliases`) on st2 core level: https://github.com/StackStorm/st2/issues/3973 Filtering specific Aliases on Hubot level might be less popular functionality, comparing to...

Thanks for the report, It's caused by outdated dependencies we're using in https://github.com/StackStorm/st2client.js Related PR that failed to update it: https://github.com/StackStorm/st2client.js/pull/68 This is still a valid issue.