lib/oci/core/virtual_network_client.rb
# Creates a new IPSec connection between the specified DRG and CPE. For more information, see
# [IPSec VPNs](https://docs.cloud.oracle.com/Content/Network/Tasks/managingIPsec.htm).
#
# If you configure at least one tunnel to use static routing, then in the request you must provide
# at least one valid static route (you're allowed a maximum of 10). For example: 10.0.0.0/16.
# If you configure both tunnels to use BGP dynamic routing, you can provide an empty list for
# the static routes. For more information, see the important note in
# {IPSecConnection}.
#
# For the purposes of access control, you must provide the OCID of the compartment where you want the
# IPSec connection to reside. Notice that the IPSec connection doesn't have to be in the same compartment
# as the DRG, CPE, or other Networking Service components. If you're not sure which compartment to
# use, put the IPSec connection in the same compartment as the DRG. For more information about
# compartments and access control, see
# [Overview of the IAM Service](https://docs.cloud.oracle.com/Content/Identity/Concepts/overview.htm).
# For information about OCIDs, see [Resource Identifiers](https://docs.cloud.oracle.com/Content/General/Concepts/identifiers.htm).
#
# You may optionally specify a *display name* for the IPSec connection, otherwise a default is provided.
# It does not have to be unique, and you can change it. Avoid entering confidential information.
#
# After creating the IPSec connection, you need to configure your on-premises router
# with tunnel-specific information. For tunnel status and the required configuration information, see:
#
#   * {IPSecConnectionTunnel}
#   * {IPSecConnectionTunnelSharedSecret}
#
# For each tunnel, you need the IP address of Oracle's VPN headend and the shared secret
# (that is, the pre-shared key). For more information, see
# [Configuring Your On-Premises Router for an IPSec VPN](https://docs.cloud.oracle.com/Content/Network/Tasks/configuringCPE.htm).
#
# @param [OCI::Core::Models::CreateIPSecConnectionDetails] create_ip_sec_connection_details Details for creating an `IPSecConnection`.
# @param [Hash] opts the optional parameters
# @option opts [OCI::Retry::RetryConfig] :retry_config The retry configuration to apply to this operation. If no key is provided then the service-level
#   retry configuration defined by {#retry_config} will be used. If an explicit `nil` value is provided then the operation will not retry
# @option opts [String] :opc_retry_token A token that uniquely identifies a request so it can be retried in case of a timeout or
#   server error without risk of executing that same action again. Retry tokens expire after 24
#   hours, but can be invalidated before then due to conflicting operations (for example, if a resource
#   has been deleted and purged from the system, then a retry of the original creation request
#   may be rejected).
#
# @return [Response] A Response object with data of type {OCI::Core::Models::IPSecConnection IPSecConnection}
Creates a new IPSec connection between the specified DRG and CPE.

If you configure at least one tunnel to use static routing, then in the request you must provide
at least one valid static route (you're allowed a maximum of 10).

For the purposes of access control, you must provide the OCID of the compartment where you want the
IPSec connection to reside. Notice that the IPSec connection doesn't have to be in the same compartment
as the DRG, CPE, or other Networking Service components. If you're not sure which compartment to
use, put the IPSec connection in the same compartment as the DRG. For more information about
compartments and access control, see
[Overview of the IAM Service].
For information about OCIDs, see [Resource Identifiers].

You may optionally specify a *display name* for the IPSec connection, otherwise a default is provided.
It does not have to be unique, and you can change it. Avoid entering confidential information.

After creating the IPSec connection, you need to configure your on-premises router
with tunnel-specific information. For tunnel status and the required configuration information, see.



For each tunnel, you need the IP address of Oracle's VPN headend and the shared secret
(that is, the pre-shared key). For more information, see
[Configuring Your On-Premises Router for an IPSec VPN].
Creates a new IPSec connection between the specified DRG and CPE . If you configure at least one tunnel to use static routing then in the request you must provide at least one valid static route ( you ' re allowed a maximum of 10 ) . For the purposes of access control you must provide the OCID of the compartment where you want the IPSec connection to reside . Notice that the IPSec connection doesn ' t have to be in the same compartment as the DRG CPE or other Networking Service components . If you ' re not sure which compartment to use put the IPSec connection in the same compartment as the DRG . For more information about compartments and access control see [ Overview of the IAM Service ] . For information about OCIDs see [ Resource Identifiers ] . You may optionally specify a * display name * for the IPSec connection otherwise a default is provided . It does not have to be unique and you can change it . Avoid entering confidential information . After creating the IPSec connection you need to configure your on - premises router with tunnel - specific information . For tunnel status and the required configuration information see . For each tunnel you need the IP address of Oracle ' s VPN headend and the shared secret ( that is the pre - shared key ) . For more information see [ Configuring Your On - Premises Router for an IPSec VPN ] .
def create_ip_sec_connection(create_ip_sec_connection_details, opts = {})
      logger.debug 'Calling operation VirtualNetworkClient#create_ip_sec_connection.' if logger
      raise "Missing the required parameter 'create_ip_sec_connection_details' when calling create_ip_sec_connection." if create_ip_sec_connection_details.nil?
      path = '/ipsecConnections'
      operation_signing_strategy = :standard
      query_params = {}
      header_params = {}
      header_params[:accept] = 'application/json'
      header_params[:'content-type'] = 'application/json'
      header_params[:'opc-retry-token'] = opts[:opc_retry_token] if opts[:opc_retry_token]
      header_params[:'opc-retry-token'] ||= OCI::Retry.generate_opc_retry_token
      post_body = @api_client.object_to_http_body(create_ip_sec_connection_details)
      OCI::Retry.make_retrying_call(applicable_retry_config(opts), call_name: 'VirtualNetworkClient#create_ip_sec_connection') do
        @api_client.call_api(
          :POST,
          path,
          endpoint,
          header_params: header_params,
          query_params: query_params,
          operation_signing_strategy: operation_signing_strategy,
          body: post_body,
          return_type: 'OCI::Core::Models::IPSecConnection'
        )
      end
    end
def create_ip_sec_connection ( create_ip_sec_connection_details , opts = { } ) logger . debug 'Calling operation VirtualNetworkClient#create_ip_sec_connection.' if logger raise "Missing the required parameter 'create_ip_sec_connection_details' when calling create_ip_sec_connection." if create_ip_sec_connection_details . nil? path = '/ipsecConnections' operation_signing_strategy = :standard query_params = { } header_params = { } header_params [ :accept ] = 'application/json' header_params [ :' content-type ' ] = 'application/json' header_params [ :' opc-retry-token ' ] = opts [ :opc_retry_token ] if opts [ :opc_retry_token ] header_params [ :' opc-retry-token ' ] ||= OCI :: Retry . generate_opc_retry_token post_body = @api_client . object_to_http_body ( create_ip_sec_connection_details ) OCI :: Retry . make_retrying_call ( applicable_retry_config ( opts ) , call_name : 'VirtualNetworkClient#create_ip_sec_connection' ) do @api_client . call_api ( :POST , path , endpoint , header_params : header_params , query_params : query_params , operation_signing_strategy : operation_signing_strategy , body : post_body , return_type : 'OCI::Core::Models::IPSecConnection' ) end end
Creates a new IPSec connection between the specified DRG and CPE.
Creates a new IPSec connection between the specified DRG and CPE .
# rubocop:disable Style/NegatedIf # Query Params # Header Params # rubocop:enable Style/NegatedIf # rubocop:disable Metrics/BlockLength # rubocop:enable Metrics/BlockLength
A Response object with data of type {OCI::Core::Models::IPSecConnection IPSecConnection}
A Response object with data of type { OCI :: Core :: Models :: IPSecConnection IPSecConnection }
Response
create_ip_sec_connection_details
<not_specific>
opts
:opc_retry_token A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of executing that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations (for example, if a resource has been deleted and purged from the system, then a retry of the original creation request may be rejected).
: opc_retry_token A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of executing that same action again . Retry tokens expire after 24 hours but can be invalidated before then due to conflicting operations ( for example if a resource has been deleted and purged from the system then a retry of the original creation request may be rejected ) .
<not_specific>
opts the optional parameters
opts the optional parameters