feat(akamai): add Guardicore Segmentation, restructure Edge DNS into its own folder - #75
Merged
michaelelrom merged 6 commits intoAug 17, 2026
Conversation
…o Project Adds an OpenAPI spec for Akamai Guardicore Segmentation, built from the official terraform-provider-guardicore-segmentation source, plus 55 workflows covering labels, label groups, policy groups, policy rules, DNS security, assets, worksites, user groups, incidents, and agent aggregators.
…ric spec title Moves the existing Akamai Edge DNS assets into Akamai/Edge DNS/ to match the per-product folder pattern used elsewhere (Infoblox, F5, ServiceNow). Also renames the spec's title from the generic "Akamai APIs" to "Akamai Edge DNS API" and tightens its description to be product-specific.
…vention Renames akamai_apis-*.json to akamai_edge_dns_api-*.json to match the <vendor>_<product>_api-<version>.json pattern used across the repo.
…uardicore instance Updates all 55 workflows' adapter_id from Guardicore to Akamai Guardicore to match the renamed integration instance.
Adds 60 workflows covering zones, zone versions, record sets, change lists, TSIG keys, bulk zone requests, zone status checks, and DNS reference data, backed by the existing Edge DNS Integration Model.
…ntation spec and README
michaelelrom
changed the title
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
2 participants
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.
Summary
terraform-provider-guardicore-segmentationsource, plus a Studio Project with 55 workflows across 10 folders (labels, label groups, policy groups, policy rules, DNS security, assets, worksites, user groups, incidents, agent aggregators)Akamai/Edge DNS/folder to match the per-product pattern used elsewhere (Infoblox, F5, ServiceNow), renames the spec files/title for consistency, and adds a new Studio Project with 60 workflows across 8 folders (zones, zone versions, record sets, change lists, TSIG keys, bulk zone requests, zone status checks, DNS reference data)Test plan
-latest.jsonspecs as Integration ModelsAkamai GuardicoreandAkamai Edge DNSintegration instances against live environments