Draft
Conversation
Lists all exact adapter type strings across aws, azure, gcp, and stdlib sources. Focuses on cross-source naming differences for similar concepts (IAM roles, compute instances, disks, networking, KMS, etc.) and includes a common-mistakes section to prevent wrong name selection. Co-authored-by: TP Honey <thomas.honey@overmind.tech>
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.
What
Adds
adapter-naming-conventions.md— a reference file that lists every adapter type string across all four sources (aws, azure, gcp, stdlib) and documents how similar concepts are named differently across providers.Why
An agent selecting adapter types frequently picks the wrong name because the same concept is expressed differently per source. For example:
iam-role(aws) vsgcp-iam-role(gcp) vsazure-authorization-role-assignment(azure)ec2-volume(aws) vsgcp-compute-disk/azure-compute-diskgcp-compute-subnetwork(notgcp-compute-subnet)gcp-cloud-kms-crypto-key(notgcp-kms-key)The file is structured for agent consumption with:
item-types.go