Skip to content
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

Align phases and actions with those provided by Rulesets API #1367

Merged

Conversation

zakcutner
Copy link
Contributor

@zakcutner zakcutner commented Aug 9, 2023

Description

  • Sort phase and actions types in alphabetical order.

  • Remove the allow action, since this does not exist.

  • Add the ddos_mitigation action.

  • Remove the http_request_main phase, since this does not exist.

  • Remove the http_response_headers_transform_managed and http_request_late_transform_managed phases, since they are not exposed publicly. The Managed Transforms API can be used to configure managed transforms.

  • Rename RulesetPhaseRateLimit and RulesetPhaseSuperBotFightMode to be consistent with the phase names.

Has your change been tested?

Passes existing tests, no new functionality has been introduced.

Types of changes

What sort of change does your code introduce/modify?

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • All new and existing tests passed.
  • This change is using publicly documented in cloudflare/api-schemas
    and relies on stable APIs.

@github-actions
Copy link
Contributor

github-actions bot commented Aug 9, 2023

changelog detected ✅

Comment on lines +17 to +23
```release-note:breaking-change
rulesets: Rename `RulesetPhaseRateLimit` to `RulesetPhaseHTTPRatelimit`, to match the phase name
```

```release-note:breaking-change
rulesets: Rename `RulesetPhaseSuperBotFightMode` to `RulesetPhaseHTTPRequestSBFM`, to match the phase name
```
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I made these changes just to be consistent with the names of the other phase types. @jacobbednarz we can revert this part if you think it's too much of a breaking change

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nope, that's perfect, thanks!

@zakcutner zakcutner marked this pull request as ready for review August 9, 2023 15:10
* Remove the `allow` action, since this does not exist.

* Add the `ddos_mitigation` action.

* Remove the `http_request_main` phase, since this does not exist.

* Remove the `http_response_headers_transform_managed` and
  `http_request_late_transform_managed` phases, since they are not
  exposed publicly. The Managed Transforms API can be used to configure
  managed transforms.

* Rename `RulesetPhaseRateLimit` and `RulesetPhaseSuperBotFightMode` to
  be consistent with the phase names.
@jacobbednarz jacobbednarz merged commit 1144b28 into cloudflare:master Aug 9, 2023
11 checks passed
@github-actions github-actions bot added this to the v0.75.0 milestone Aug 9, 2023
github-actions bot pushed a commit that referenced this pull request Aug 9, 2023
@zakcutner zakcutner deleted the zak/rulesets-phases-actions branch August 9, 2023 23:22
@github-actions
Copy link
Contributor

This functionality has been released in v0.75.0.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 15, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants