feat: Updated OpenAPI file for cloud gateway-addon.

[shivaygupta-dotcom]

Summary

In this PR,

1. We are adding changes to support cloud-gateway add on.
2. Syncing with platform-api repo.

Issues resolved

• Cloud Gateways: Implement Add-ons Managed Cache #174

Related PRs on platform-api (if any)

• https://github.com/Kong/platform-api/pull/2243

Checklist ✅

• Features being added are live
• Added/updated examples (if applicable)
• Added/updated acceptance tests (if applicable)
• Updated CHANGELOG.md to clearly mention any breaking changes, new features and bug fixes
• Clean commit history (reset to the current release (release/x.y.z) and git cherry-pick if necessary)

[harshadixit12]

@shivaygupta-dotcom have we tested what happens if the add on name is changed and we run terraform-apply?

[shivaygupta-dotcom]

@shivaygupta-dotcom have we tested what happens if the add on name is changed and we run terraform-apply?

@harshadixit12, I just tested this locally and it looks like the API treats a rename as a brand-new resource creation. Because of that, it’s hitting a restriction that prevents the update from going through.

error from API:

{"status":400,"title":"Invalid Request","instance":"kong:trace:15998110656216816935","detail":"Control plane 'b5522f7b-bb43-4b94-941e-27019b03b694' already has an add-on of kind 'managed-cache.v0'. Only one
│ add-on of a kind is allowed per control plane.","invalid_parameters":[]}

╵

[harshadixit12]

like the API treats a rename as a brand-new resource creation.

This is expected - since there is no update operation defined. Can we find out from cloud gateways team why we get this error when trying to recreate?
We can consider having a retry configured if this is expected.

[shivaygupta-dotcom]

like the API treats a rename as a brand-new resource creation.

This is expected - since there is no update operation defined. Can we find out from cloud gateways team why we get this error when trying to recreate? We can consider having a retry configured if this is expected.

Writing here for future reference:
Had discussion with cgw team, the diff which we are facing between deletion and creation while running terraform apply is expected, as while deleting addOn they use kafka events and it takes some time to process the deletion event of the addOn, while terraform expects deletion and creation in real time. This will be fixed in future when they will start support update operation.

slack thread: https://kongstrong.slack.com/archives/C090KKNC5ED/p1771828352493879?thread_ts=1770713778.491859&cid=C090KKNC5ED

[shivaygupta-dotcom]

closing this as alot of conflicts.
opening this new PR with only cgw add-on changes: #187