oci-logging

OCI NodeJS client for Logging Service

This module enables you to write code to manage resources for Logging Service.

Requirements

To use this module, you must have the following:

• An Oracle Cloud Infrastructure account.
• A user created in that account, in a group with a policy that grants the desired permissions. This can be a user for yourself, or another person/system that needs to call the API. For an example of how to set up a new user, group, compartment, and policy, see Adding Users. For a list of typical policies you may want to use, see Common Policies.
• A key pair used for signing API requests, with the public key uploaded to Oracle. Only the user calling the API should be in possession of the private key. For more information, see Configuring Credentials

Installing

Use the following command to install this module:

npm install oci-logging

Alternatively you can git clone this repo.

Changelog

2.75.0 - 2023-12-04

Added

• Support for calling Oracle Cloud Infrastructure services in the eu-dcc-zurich-1 and the sa-bogota-1 region
• Support for managing certificates of target Servers in the Golden Gate service
• Support for AWR Hub Snapshot ingest endpoints in the Operations Insights service
• Support for reducing false positives in the Application Dependency Management service
• Support for ARM shapes in the Data Science service
• Support for new optional parameters in the upload discovery data API in the Usage service
• Support for multiple clusters in a Software-Defined Data Centers (SDDCs) in the VMWare Solution service
• Support for No/Zero days backup in Autonomous Container Database in the Database service
• Support for provisioning a VM Cluster with a choice of Exadata image version in the Database service
• Support for updating ocpu/ecpu count, local storage, ACD count and Exadata storage on Cloud Autonomous VM Cluster and Autonomous VM Cluster in the Database service
• Support for serial console history in the Database service
• Support for Oracle Linux 8 version database system in the Database service

Breaking Changes

• Fields sddcId, currentSku, nextSku, were renamed to clusterId, currentCommitment, nextCommitment in models CreateEsxiHostDetails, EsxiHost and EsxiHostSummary in the VMWare Solution service
• Field failedEsxiHostId was removed from CreateEsxiHostDetails model in the VMWare Solution service
• Field nonUpgradedEsxiHostId was renamed to EsxiSoftwareVersion in CreateEsxiHostDetails model in the VMWare Solution service
• Field esxiHostsCount was removed from CreateEsxiHostDetails model in the VMWare Solution service
• Fields provisioningSubnetId, vsphereVlanId, vmotionVlanId, vsanVlanId, nsxVTepVlanId, nsxEdgeVTepVlanId, nsxEdgeUplink1VlanId, nsxEdgeUplink2VlanId, instanceDisplayNamePrefix, initialSku, isHcxEnabled, hcxVlanId, isHcxEnterpriseEnabled were removed from CreateSddcDetails model in the VMWare Solution service
• Fields vsphereVlanId, vmotionVlanId, vsanVlanId, nsxVTepVlanId, nsxEdgeVTepVlanId, nsxEdgeUplink1VlanId, nsxEdgeUplink2VlanId, replicationVlanId, provisioningVlanId, hcxVlanId were removed from UpdateSddcDetails model in the VMWare Solution service
• Fields supportedSddcTypes and isSupportMonthlySku were removed from SupportedHostShapeSummary model in the VMWare Solution service
• Field computeAvailabilityDomain was removed from Sddc and SddcSummary models in the VMWare Solution service
• Field sddcType was removed from ListSupportedHostShapesRequest model in the VMWare Solution service