AS3 Per App API promoted from beta to general availability

Поділитися
Вставка
  • Опубліковано 14 гру 2024

КОМЕНТАРІ • 6

  • @JohnSmith-dg3rd
    @JohnSmith-dg3rd 10 місяців тому

    I'm excited for BIG-IP Next. Finally something new.

    • @MarkDittmer
      @MarkDittmer  10 місяців тому

      definitely. Lots of new content coming.

  • @sliddjur
    @sliddjur 9 місяців тому

    Ive been following your videos about as3 per app api, and now you suddenly changed your wording to resource group (aka tenant, aka partition) is the legacy way of doing everything? :)
    So you can not use /declare/tenant123/app and declare a single app, when tenant123 is not declared already?
    Also, how do you delete a single app?

    • @MarkDittmer
      @MarkDittmer  9 місяців тому

      thank you. No Per-app declaration must contain at least one application
      Declare one app in tenant123 and then you can POST to /declare/tenant123/applications/ with updates

  • @quickref
    @quickref 10 місяців тому

    We are currently preparing to migrate our existing f5 applications to AS3 and since we have some clusters with a lot of virtual servers, Per App will be helpful to keep a better control of our applications. Will there be an option to transform a ucs file with ACC to AS3 Per App? I'm planning to attend the Berlin App world. Will you be there, too?

    • @MarkDittmer
      @MarkDittmer  10 місяців тому +3

      Journey's can consume the UCS file and represent the configuration as a per-app. But Journey's wont POST the the App back to BIG-IP using Per-APP. However this could be better implemented in the VScode extenetion. I am working with that team to get the Per-App API added to VScode