Threat control LWRP #6
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…udFlare * Stores last action in a node attribute cache, CF API is only called once per day, or if status changes * IP attribute defaults to current's node IP address
|
|
||
| private | ||
|
|
||
| # this needs to be done at run time, not compile time |
There was a problem hiding this comment.
Blargh. DRY that up in a lib file FFS.
There was a problem hiding this comment.
Implying I should refactor that bit in the dns_record resource as well?
…grant self-contained testing
|
Re-factored and merged as #7 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cf. first commit and README changes:
Add a threat_control LWRP, allowing to whitelist/blacklist IPs on CloudFlare