Refactor

[slpsys]

Fixing an issue with environments, refactoring a bit, adding specs, and bumping to 1.0, because I'm breaking retry. It used to be a synonym for constant retry intervals, but this was non-optimal for use with environments, because Pester.aws.retry {} (which seems straightforward) would always force constant, regardless of what you chose in the environment config. That's pretty dumb, so I'm renaming the old behavior retry_constant, and letting retry defer to your environment, which is IMO the way to go for config.

@apurvis @dtboctor

[slpsys]

rake prep / rake rubocop also now passes

[apurvis]

i like verboseness

[slpsys]

eh?

[dtboctor]

so did you make rubocop pass by lowering all it's standards?

[apurvis]

i like that it's retry_constant instead of just retry, and retry is the baseline that you have to setup w/yr own behavior

[slpsys]

@dtboctor no, I fixed all of the issues outside of retry_action (which has specs and hasn't changed in almost two years), and lowered the thresholds to exactly retry_action's levels. that's just like..how complex it is, given the features--i'm not real convinced it'd be easy or useful to break up at this point.

@apurvis ah, wasn't sure which way that went