CREATEVIRTUALCLUSTER()`¶

About CreateVirtualCluster¶

Creates a virtual cluster. Virtual cluster is a managed entity on Amazon EMR on EKS. You can create, describe, list and delete virtual clusters. They do not consume any additional resource in your system. A single virtual cluster maps to a single Kubernetes namespace. Given this relationship, you can model virtual clusters the same way you model Kubernetes namespaces to meet your requirements.

Method Signature¶

METHODS /AWS1/IF_EMC~CREATEVIRTUALCLUSTER
  IMPORTING
    !IV_NAME TYPE /AWS1/EMCRESOURCENAMESTRING OPTIONAL
    !IO_CONTAINERPROVIDER TYPE REF TO /AWS1/CL_EMCCONTAINERPROVIDER OPTIONAL
    !IV_CLIENTTOKEN TYPE /AWS1/EMCCLIENTTOKEN OPTIONAL
    !IT_TAGS TYPE /AWS1/CL_EMCTAGMAP_W=>TT_TAGMAP OPTIONAL
    !IV_SECURITYCONFIGURATIONID TYPE /AWS1/EMCRESOURCEIDSTRING OPTIONAL
  RETURNING
    VALUE(OO_OUTPUT) TYPE REF TO /aws1/cl_emccrevirtualclustrsp
  RAISING
    /AWS1/CX_EMCEKSREQTHROTTLEDEX
    /AWS1/CX_EMCINTERNALSERVEREX
    /AWS1/CX_EMCRESOURCENOTFOUNDEX
    /AWS1/CX_EMCVALIDATIONEX
    /AWS1/CX_EMCCLIENTEXC
    /AWS1/CX_EMCSERVEREXC
    /AWS1/CX_RT_TECHNICAL_GENERIC
    /AWS1/CX_RT_SERVICE_GENERIC.

IMPORTING¶

Required arguments:¶

`iv_name` `TYPE /AWS1/EMCRESOURCENAMESTRING` `/AWS1/EMCRESOURCENAMESTRING`¶

The specified name of the virtual cluster.

`io_containerprovider` `TYPE REF TO /AWS1/CL_EMCCONTAINERPROVIDER` `/AWS1/CL_EMCCONTAINERPROVIDER`¶

The container provider of the virtual cluster.

`iv_clienttoken` `TYPE /AWS1/EMCCLIENTTOKEN` `/AWS1/EMCCLIENTTOKEN`¶

The client token of the virtual cluster.

Optional arguments:¶

`it_tags` `TYPE /AWS1/CL_EMCTAGMAP_W=>TT_TAGMAP` `TT_TAGMAP`¶

The tags assigned to the virtual cluster.

`iv_securityconfigurationid` `TYPE /AWS1/EMCRESOURCEIDSTRING` `/AWS1/EMCRESOURCEIDSTRING`¶

The ID of the security configuration.

RETURNING¶

`oo_output` `TYPE REF TO /aws1/cl_emccrevirtualclustrsp` `/AWS1/CL_EMCCREVIRTUALCLUSTRSP`¶

Examples¶

Syntax Example¶

This is an example of the syntax for calling the method. It includes every possible argument and initializes every possible value. The data provided is not necessarily semantically accurate (for example the value "string" may be provided for something that is intended to be an instance ID, or in some cases two arguments may be mutually exclusive). The syntax shows the ABAP syntax for creating the various data structures.

DATA(lo_result) = lo_client->createvirtualcluster(
  io_containerprovider = new /aws1/cl_emccontainerprovider(
    io_info = new /aws1/cl_emccontainerinfo(
      io_eksinfo = new /aws1/cl_emceksinfo(
        iv_namespace = |string|
        iv_nodelabel = |string|
      )
    )
    iv_id = |string|
    iv_type = |string|
  )
  it_tags = VALUE /aws1/cl_emctagmap_w=>tt_tagmap(
    (
      VALUE /aws1/cl_emctagmap_w=>ts_tagmap_maprow(
        key = |string|
        value = new /aws1/cl_emctagmap_w( |string| )
      )
    )
  )
  iv_clienttoken = |string|
  iv_name = |string|
  iv_securityconfigurationid = |string|
).

This is an example of reading all possible response values

lo_result = lo_result.
IF lo_result IS NOT INITIAL.
  lv_resourceidstring = lo_result->get_id( ).
  lv_resourcenamestring = lo_result->get_name( ).
  lv_virtualclusterarn = lo_result->get_arn( ).
ENDIF.

/AWS1/IF_EMC=>CREATEVIRTUALCLUSTER()¶