Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    TomaAlexandru
    @TomaAlexandru
    .
    Govinda Fichtner
    @Govinda-Fichtner
    Hi guys, seems still to be pretty empty here. :)
    mflorin
    @mflorin
    Yup, silence :)
    Guilherme Prado
    @gprado-ionos
    Hi everyone. Good morning. I started using the SDK and I have question. Is it possible to make composite post calls using the SDK? For example, I want to POST a server with a volume and a nic, but it seems I need to post those entities individually.
    mihaela-mh
    @mihaela-mh

    Hello,

    Yes, you can make composite calls using the SDK. For the provided example (POST a server with a VOLUME and a NIC), using the Java SDK, you will have to use this method. The Server object has a field named ServerEntities , that contains cdroms, volumes, and nics. Here is where you can define the volume and the nic you want, and then call the create method. In this way, the SDK will create the attached entitites (if they do not already exist) and there will be no need of making different POST requests.

    If you need any more details, just let me know.

    Guilherme Prado
    @gprado-ionos
    Thank you! I will give it a try.
    Guilherme Prado
    @gprado-ionos
    @mihaela-mh I can set AttachedVolumes(https://github.com/ionos-cloud/sdk-java/blob/master/DOCS.md#AttachedVolumes) and Nics(https://github.com/ionos-cloud/sdk-java/blob/master/DOCS.md#Nics) to ServerEntities(https://github.com/ionos-cloud/sdk-java/blob/master/DOCS.md#ServerEntities), but I cannot add Items to AttachedVolumes and Nics as it is a readOnly Property.
    I run into a NPE if I try to add Volume and Nic to it.
    mihaela-mh
    @mihaela-mh
    @gprado-ionos, I reproduced it and noticed that it is a bug caused by some inconsistencies of the Cloud API swagger file, which we use to generate the SDKs
    I opened this bug ionos-cloud/sdk-java#1 on the Github repository, to be able to track the progress of this issue
    Guilherme Prado
    @gprado-ionos
    Thank you.
    mihaela-mh
    @mihaela-mh
    No problem! Also, we strongly encourage users to open bugs/feature requests on the Github repositories when needed.
    André Schulz
    @AndreSchulz-IONOS
    hi, i had a look at the v6 sdk...
    https://github.com/ionos-cloud/sdk-java/blob/8a00a79da0164bf937a0097e445b14296a1f3c45/src/main/java/com/ionoscloud/model/DatacenterProperties.java#L56
    is missing some values
    VNF_NAT("vnf-nat"),
    VNF_FW("vnf-fw"),
    VNF_LB("vnf-lb"),
    CLOUD_INIT("cloud-init"),
    CORE_VPS("core-vps"),
    if you wish i can create a bug at the public repo, but that features are currently not communicated to customers?
    7 replies
    André Schulz
    @AndreSchulz-IONOS

    https://github.com/ionos-cloud/sdk-java/blob/master/pom.xml uses <java.version>1.7</java.version>
    • the dependency okhttp uses <java.version>1.8</java.version> and OkHttpClient uses java.time.Duration

    • maven is ok with that
    • but Eclipse complains about that: he type java.time.Duration cannot be resolved. It is indirectly referenced from required .class files and will not work until you set <java.version>1.8</java.version>

    André Schulz
    @AndreSchulz-IONOS
    https://github.com/ionos-cloud/sdk-java/tree/release/v6
    it would be very kind, if we would provide an enum containing all the possible HTTP response status codes
    mflorin
    @mflorin
    yes, we can do that
    Dmitrii Medvedev
    @dmedvedev-ionos
    Hi everyone!
    I have a question regarding our terraform provider
    Is it possible somehow to create more than one nic for server?
    Livius Pirvanescu
    @LiviusP
    Hi Dmitrii, I think so. But @mflorin can say for sure
    mflorin
    @mflorin
    Hi @dmedvedev-ionos , unfortunately you cannot create a server with multiple nics, however, you can create individual nics by providing the server_id. However, the server resource in the terraform state will only be aware of the nic used when the server resource was created