-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE] Promote 'ng' states #35
Comments
@daks Sounds good, these are the current deprecation steps, from previous conversions: |
# [0.17.0](v0.16.3...v0.17.0) (2019-11-27) ### Bug Fixes * **release.config.js:** use full commit hash in commit link [skip ci] ([37439c8](37439c8)) ### Continuous Integration * **kitchen:** use `debian-10-master-py3` instead of `develop` [skip ci] ([14629b9](14629b9)) * **kitchen:** use `develop` image until `master` is ready (`amazonlinux`) [skip ci] ([6652ff9](6652ff9)) * **kitchen+travis:** upgrade matrix after `2019.2.2` release [skip ci] ([9968b09](9968b09)) * **travis:** apply changes from build config validation [skip ci] ([885c517](885c517)) * **travis:** opt-in to `dpl v2` to complete build config validation [skip ci] ([5112d76](5112d76)) * **travis:** run `shellcheck` during lint job ([527cf1e](527cf1e)) * **travis:** update `salt-lint` config for `v0.0.10` [skip ci] ([52eb62c](52eb62c)) * **travis:** use build config validation (beta) [skip ci] ([2ae5e8c](2ae5e8c)) ### Documentation * **contributing:** remove to use org-level file instead [skip ci] ([2688f64](2688f64)) * **readme:** update link to `CONTRIBUTING` [skip ci] ([37c0dd1](37c0dd1)) ### Features * update deprecation version number in `semantic-release` run ([11d748a](11d748a)) * **deprecated.sls:** prepare warning state for `ng` promotion ([#35](#35)) ([4c702bc](4c702bc)) * **deprecation:** include `ng` promotion warning to all state files ([4348b59](4348b59)) ### Performance Improvements * **travis:** improve `salt-lint` invocation [skip ci] ([5a14047](5a14047))
We've got a significant blocker before this can be completed. There are a number of errors when running the |
@myii Do you mean those |
@Irsute Good catch; while using the |
OK, that's better. The ones that are broken are probably due to configuration issues. However, looking at the debug output, I've identified another bug: fail2ban-formula/fail2ban/ng/map.jinja Line 23 in d41fe3f
This is supposed to be |
And there you have it, fixed the configuration from the |
a big thanks @myii , |
@Irsute So the next few steps:
After that, the next stages of completing this issue can be looked at. |
PR is updated |
* Semi-automated using myii/ssf-formula#118 * Fix `ng:lookup` to use values that actually work
* Semi-automated using myii/ssf-formula#118 * Fix `ng:lookup` to use values that actually work
# [1.74.0](v1.73.0...v1.74.0) (2020-01-11) ### Features * **fail2ban:** use `fail2ban.ng` in Kitchen ([5a5df71](5a5df71)), closes [/github.com/saltstack-formulas/fail2ban-formula/issues/35#issuecomment-573162677](https://github.com//github.com/saltstack-formulas/fail2ban-formula/issues/35/issues/issuecomment-573162677)
* Close saltstack-formulas#34 * Close saltstack-formulas#35
* Close saltstack-formulas#34 * Close saltstack-formulas#35
* Close saltstack-formulas#34 * Close saltstack-formulas#35 BREAKING CHANGE: all previous `fail2ban` based configurations must be reviewed; `fail2ban.ng` usage must be promoted to `fail2ban` and any uses of the original `fail2ban` will have to be converted.
* Semi-automated using myii/ssf-formula#119 * Close saltstack-formulas#34 * Close saltstack-formulas#35 BREAKING CHANGE: all previous `fail2ban` based configurations must be reviewed; `fail2ban.ng` usage must be promoted to `fail2ban` and any uses of the original `fail2ban` will have to be converted.
good job @myii |
# [1.0.0](v0.17.2...v1.0.0) (2020-01-13) ### Features * promote `ng` ([fb1ae56](fb1ae56)), closes [#34](#34) [#35](#35) ### BREAKING CHANGES * all previous `fail2ban` based configurations must be reviewed; `fail2ban.ng` usage must be promoted to `fail2ban` and any uses of the original `fail2ban` will have to be converted.
🎉 This issue has been resolved in version 1.0.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Is your feature request related to a problem?
No
Describe the solution you'd like
Now that this formula has semantic versioning, I think it's time to start deprecating
fail2ban.ng
and then promote it tofail2ban
which means remove all legacy code.Steps:
fail2ban.ng
is deprecatedfail2ban.ng
states tofail2ban
Describe alternatives you've considered
none
Additional context
This has already been done for
nginx-formula
and others (but I don't know which).The text was updated successfully, but these errors were encountered: