fix: move HashiCorp, 1Password, 6connect into Vendor/Product directory structure - #102
Merged
Merged
Conversation
…y structure Same pattern as NetScaler/ADC and Cisco/IOS: Vault, Connect, and Provision are HashiCorp's, 1Password's, and 6connect's actual product names respectively, distinct from the vendor/company name — matches the STANDARDS.md convention even for a currently-single-product vendor. No content changes, only paths.
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.
Same class of fix as the Ansible restructure in PR #101:
Vault,Connect, andProvisionare the actual product names for HashiCorp, 1Password, and 6connect respectively — distinct from the vendor/company name, same relationship asNetScaler/ADCorCisco/IOS. STANDARDS.md's "single-product vendors are flattened" rule technically covers this, but existing precedent (NetScaler/ADC) keeps the Product folder whenever the product has its own distinct name, even as the vendor's only product.HashiCorp/OpenAPIs/→HashiCorp/Vault/OpenAPIs/1Password/OpenAPIs/→1Password/Connect/OpenAPIs/6connect/OpenAPIs/→6connect/Provision/OpenAPIs/Path/file moves only — no content changes.
Note: PR #101 (Studio Project backlog) also moves 6connect into this same structure independently, since it added a 6connect Studio Project on its own branch. Whichever of these two PRs merges first, the other should resolve as a clean no-op rename on the same destination path — but worth a quick check at merge time.
Considered but not changed: ARIN (RDAP + Whois-RWS) and Selector (Metastore Inventory + Query) each ship two OpenAPI specs under one flat vendor folder too, but on inspection these are two API surfaces of one cohesive product/use case (ARIN's README explicitly frames them as one paired Studio Project; same pattern as Cisco ISE's 25 module specs or NDFC's LAN/SAN specs living under one product folder) — not two separately-branded product lines the way Vault/Connect/Provision are. Left those alone.