Kong / Kong/developer.konghq.com
Cloud Gateways: VPC Peering and Transit Gateway ID returned in API response
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 28
- Forks
- 121
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 313
Description
Definition of done
- Update the following docs with updated steps (and test!) now that the VPC peering and transit gateway IDs are returned in the API response:
[!IMPORTANT]
This is a Konnect release PR and should be handed off to the PM to merge with the release once complete. Make sure you follow the Konnect release checklist.
Information
DRP: Josh W.
Aha: https://konghq.aha.io/features/CGW-9
Notes: "This will be covered as a part of the v2-v3 migration."
Due date (optional)
?
Size
Small
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the two linked documentation pages: create-transit-gateway-with-operator-and-aws and dedicated-cloud-gateways/gcp-vpc-peering, then review the Konnect release checklist. Update the steps and test them against the API response containing the VPC peering and transit gateway IDs; hand the completed release work to the PM for merging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, gcp
- Domain
- cloud, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100