feat(google_fastly_waf): Allow migrating away from EdgeDeployment APIs#465
Merged
Tibap merged 8 commits intoMay 19, 2026
Merged
Conversation
…geDeployment-APIs
Contributor
Release plan
|
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
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.
Description
Adds a
legacy_edge_deploymentvariable to allow choosing between the legacy SigSci EdgeDeployment APIs and the newer Fastly APIs. This enables existing services to adopt the latest version without requiring an immediate migration away from the legacy backend.With new Fastly's APIs:
product_enablementis used to enabled ngwafEdgeDeploymentresources are no longer supportedreq.http.X-Sigsci-Response-Headers = "true"are not needed anymoreEdge Securitydictionary is replaced by the new productenablementsectionRelated Tickets & Documents