API Access Control Onboarding Audit¶
This audit is the US-95 baseline for onboarding
github.com/oracle/oci-go-sdk/v65/apiaccesscontrol before services.yaml
publishes the service.
Repo Input Status¶
go.modremains pinned togithub.com/oracle/oci-go-sdk/v65 v65.110.0.v65.110.0already contains theapiaccesscontrolpackage in the module cache; the repo lackedvendor/github.com/oracle/oci-go-sdk/v65/apiaccesscontrolonly because nothing imported that package yet.pkg/sdkimports/rollout_services.gonow blank-importsgithub.com/oracle/oci-go-sdk/v65/apiaccesscontrolsogo mod vendorkeeps the package in the branch-local inputs.
SDK Audit¶
PrivilegedApiControl¶
- Full CRUD family is present:
CreatePrivilegedApiControl,GetPrivilegedApiControl,ListPrivilegedApiControls,UpdatePrivilegedApiControl, andDeletePrivilegedApiControl. - Additional mutator is present:
ChangePrivilegedApiControlCompartment. GetPrivilegedApiControlResponsereturnsPrivilegedApiControl.ListPrivilegedApiControlsResponsereturnsPrivilegedApiControlCollectionwith[]PrivilegedApiControlSummary.ListPrivilegedApiControlsRequestexposescompartmentId,id,lifecycleState,displayName, andresourceType, plus page and sort controls.- Lifecycle states are
CREATING,UPDATING,ACTIVE,DELETING,DELETED,FAILED, andNEEDS_ATTENTION. CreatePrivilegedApiControlResponsereturns the resource body andOpcWorkRequestId.UpdatePrivilegedApiControlResponseandDeletePrivilegedApiControlResponseexposeOpcWorkRequestId; delete does not return a resource body.- The package also exposes service-local
GetWorkRequest,ListWorkRequests,ListWorkRequestErrors, andListWorkRequestLogshelpers.
Auxiliary Families¶
- Additional SDK-discovered families are
ApiMetadata,ApiMetadataByEntityType,PrivilegedApiRequest,WorkRequest,WorkRequestError, andWorkRequestLog. PrivilegedApiRequestis create/get/list only and carries separate approval, revoke, reject, and close action APIs, so it should stay unpublished initially.ApiMetadataandApiMetadataByEntityTypeare read-only support surfaces.
Generator Implications For US-96¶
PrivilegedApiControlis the requested initial kind and the only full CRUD family aligned with the follow-on story.- Recommended
formalSpecisprivilegedapicontrol. - Recommended async classification is
workrequestwithworkRequest.source=service-sdkand phasescreate,update, anddelete. PrivilegedApiControllooks viable as a direct controller-backed generated rollout because GET/list expose stable lifecycle state while the SDK also ships the work-request helpers needed to follow mutating operations.US-96should keepPrivilegedApiRequest, approval actions, and metadata auxiliaries unpublished initially and record any unsupported follow-on behavior explicitly inlogic-gaps.md.
Provider-Facts Coverage¶
formal/sources.lockpins provider facts togithub.com/oracle/terraform-provider-oci@eb653febb1bab4cc6650a96d404a8baf36fdf671.- Matching provider surfaces are
oci_apiaccesscontrol_privileged_api_controlas the resource,oci_apiaccesscontrol_privileged_api_controlas the singular data source, andoci_apiaccesscontrol_privileged_api_controlsas the list data source. - The provider docs also publish lifecycle
stateplus explicit create, update, and delete timeouts, which matches the SDK's workrequest-backed mutation shape.