Repository navigation
feat(oci): Organizations and child tenancies in the Cloud Explorer - #474
Merged
Merged
Conversation
Contributor
[Medium impact] The PR appears safe to merge; the previous finding is fixed and no new actionable issues were found.
|
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.
Summary
Adds OCI Organizations to the Cloud Explorer, read only. One
organizationsservice lists the organization, its member tenancies, the links between the parent and each child, and the invitations the tenancy sent or received, with a Kind filter and an empty state. Each row opens in the inspector.OciOrganizationsAdapteron the OCI runtime client, API version20230401, withorganizationsSchema.tsand a catalog row under Provisioning.operation_not_supported.Closes #441
Type of change
feat:)Area
packages/api)Verification
OCI Organizations against Floci-OCI. A fresh runtime lists empty. After creating a child tenancy and an invitation, the list, the Kind filter, search and inspect match the runtime responses. A received invitation was checked with an outside sender. An unknown kind or id is a 400, a missing record a 404. The empty and populated views were rendered in the browser with no console errors. README matrix regenerated, not hand edited.
Checklist
pnpm lint,pnpm type-check,pnpm test, andpnpm buildpass locallybun testinpackages/api)