oci-cims

OCI NodeJS client for Cims Service

This module enables you to write code to manage resources for Cims 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-cims

Alternatively you can git clone this repo.

Changelog

2.69.0 - 2023-08-29

Added

• Support for creating and updating network monitors in the Application Performance Monitoring Synthetics service
• Support for integration of GoldenGate service for replication in the Database Migration Service
• Support for displaying resource usage information on autonomous container database and cloud autonomous vm cluster get operations in the Database service
• Support for FastConnect Media Access Control Security (MACSec) fail open option in the Network Monitoring service
• Support for generic bare metal types and configuration maps in compute instance platform configuration in the Compute service
• Support for encrypted FastConnect in the Network Monitoring service
• Support for new parameters on customer premises equipment and virtual circuit create operations in the Network Monitoring service
• Support for virtual circuit associated tunnels in the Network Monitoring service
• Support for additional parameters on dynamic routing gateway create and update operations in the Network Monitoring service
• Support for assigning an IPv6 address to a compute instance during instance launch or secondary VNIC attach in the Compute service

Breaking Changes

• The models AnalyticsCluster, AddAnalyticsClusterDetails, AnalyticsClusterMemoryEstimate, AnalyticsClusterMemoryEstimateStatus, AnalyticsClusterNode, AnalyticsClusterSchemaMemoryEstimate, AnalyticsClusterSummary, AnalyticsClusterTableMemoryEstimate, UpdateAnalyticsClusterDetails were removed in the MySQL Database service
• The request classes AddAnalyticsClusterRequest, DeleteAnalyticsClusterRequest, GenerateAnalyticsClusterMemoryEstimateRequest, GetAnalyticsClusterRequest, RestartAnalyticsClusterRequest, StartAnalyticsClusterRequest, StopAnalyticsClusterRequest, UpdateAnalyticsClusterRequest were removed in the MySQL Database service
• The response classes DeleteAnalyticsClusterResponse, GetAnalyticsClusterMemoryEstimateResponse, RestartAnalyticsClusterResponse, StartAnalyticsClusterResponse, StopAnalyticsClusterResponse, UpdateAnalyticsClusterResponse were removed in the MySQL Database service
• The properties IsAnalyticsClusterAttached and AnalyticsCluster were removed from DbSystem and DbSystemSummary models in the MySQL Database service
• The enum member ANALYTICSCLUSTER was removed from the enum IsSupportedForEnum in the models ShapeSummary and request class ListShapesRequest in the MySQL Database service
• The enum members ADD_ANALYTICS_CLUSTER, UPDATE_ANALYTICS_CLUSTER, DELETE_ANALYTICS_CLUSTER, START_ANALYTICS_CLUSTER, STOP_ANALYTICS_CLUSTER, RESTART_ANALYTICS_CLUSTER, GENERATE_ANALYTICS_CLUSTER_MEMORY_ESTIMATE were removed from the enum WorkRequestOperationType in the MySQL Database service
• The property isAnalyticsClusterAttached was removed from the model ListDbSystemsRequest in the MySQL Database service
• The operations addAnalyticsCluster, deleteAnalyticsCluster, generateAnalyticsClusterMemoryEstimate, getAnalyticsCluster, getAnalyticsClusterMemoryEstimate, restartAnalyticsCluster, startAnalyticsCluster, stopAnalyticsCluster, updateAnalyticsCluster were removed from the DbSystemClient in the MySQL Database service