Deprecate or Revive stagnant packs

[nzlosh]

Background

Following the work performed in #153 some packs were identified as being so stagnant that the effort required to bring them up to a healthy state may be too much. This issue is to open a discussion as to the decision to deprecate or revive the pack.

Stagnant Packs

The below packs have been identified for review.

• stackstorm-aws - reference Exchange CI failures #153 (comment)
• stackstorm-openstack - reference Exchange CI failures #153 (comment)
• stackstorm-kafka - reference Exchange CI failures #153 (comment)
• stackstorm-rackspace - reference Exchange CI failures #153 (comment)
• stackstorm-azure - reference Exchange CI failures #153 (comment)
• stackstorm-telegram - reference Exchange CI failures #153 (comment)
• stackstorm-tesla - reference Exchange CI failures #153 (comment)
• stackstorm-qualys - reference Exchange CI failures #153 (comment)
• stackstorm-phantomjs - reference Exchange CI failures #153 (comment)
• stackstorm-mssql - reference Exchange CI failures #153 (comment)

[cognifloyd]

I have a forked version of the kafka pack that we're using. I can get that updated eventually.