PR progress checklist (to be filled in by reviewers)

• Changes to documentation are appropriate (or tick if not required)
• Changes to tests are appropriate (or tick if not required)
• Reviews completed

What type of PR is this?

Primary type

• [build] Changes related to the build system
• [chore] Changes to the build process or auxiliary tools and libraries such as documentation generation
• [ci] Changes to the continuous integration configuration
• [feat] A new feature
• [fix] A bug fix
• [perf] A code change that improves performance
• [refactor] A code change that neither fixes a bug nor adds a feature
• [revert] A change used to revert a previous commit
• [style] Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.)

Secondary type

• [docs] Documentation changes
• [test] Adding missing or correcting existing tests

Does this PR introduce a BREAKING CHANGE?

No.

Related issues and/or pull requests

• Semi-automated by feat(fail2ban): add notification about upcoming ng promotion myii/ssf-formula#104
• Semi-automated by feat(travis): run shellcheck during lint job myii/ssf-formula#106
• Provides first two steps for [FEATURE] Promote 'ng' states #35

Describe the changes you're proposing

Based on the deprecation done for the php-formula, as outlined here:

• [FEATURE] Promote ng version #34 (comment)

The first two PRs are merged together here.

Pillar / config required to test the proposed changes

N/A.

Debug log showing how the proposed changes work

Deprecation warning can be seen in Travis logs.

Documentation checklist

• Updated the README (e.g. Available states).
• Updated pillar.example.

Testing checklist

• Included in Kitchen (i.e. under state_top).
• Covered by new/existing tests (e.g. InSpec, Serverspec, etc.).
• Updated the relevant test pillar.

Additional context