Very handy! Nice to eliminate the need to repost a potentially huge declaration and instead just post an incremental application within a specified tenant. Super cool. Well done!
Thank you very much. I believe per-application simplifies AS3 usage. However it’s still best to GET the entire declaration which will be the source of truth. This could be POSTed as part of the your pipeline
That’s very cool . I am just curious the AS3 best practices suggest POST over PATCH for better performance . Incremental update is so cool , but is it similar to PATCH ing internally or merging the json payloads and sending a POST with merged json ?
Don’t recommend using JSON PATCH now with pet-app API. You right it’s similar but now you can POST your updates. After POSTing you can get the declaration and update your source of trough. We will be doing performance once we gather all the feedback from the beta. Let me know if you want to test this new feature. Send me a email at m.dittmer@f5.com
Thanks for this, Mark. Would this provide performance improvements? Consider the case of POSTing 1 app to a tenant which already has 9 other apps (with per-app API), vs POSTing a tenant with all 10 apps in it (with the old way) - does using the Per-App API mean AS3 only process the 1 additional app, hence can respond quicker?
Definitely. We also plan to focus on performance improvements after the beta. The hope is that POSTing a small update to the API would be less impactful than posting an entire declaration. Look forward to getting lots of amazing feedback on September 12th when AS3-47 is posted.
Very handy! Nice to eliminate the need to repost a potentially huge declaration and instead just post an incremental application within a specified tenant. Super cool. Well done!
Thank you very much. I believe per-application simplifies AS3 usage. However it’s still best to GET the entire declaration which will be the source of truth. This could be POSTed as part of the your pipeline
This looks Cool. :-), We can properly segregate Apps within the tenants.
That’s very cool . I am just curious the AS3 best practices suggest POST over PATCH for better performance . Incremental update is so cool , but is it similar to PATCH ing internally or merging the json payloads and sending a POST with merged json ?
Don’t recommend using JSON PATCH now with pet-app API. You right it’s similar but now you can POST your updates. After POSTing you can get the declaration and update your source of trough. We will be doing performance once we gather all the feedback from the beta. Let me know if you want to test this new feature. Send me a email at m.dittmer@f5.com
@@MarkDittmer thanks Mark . I work for charter . Will reach out from official id as we are already using your product .
Thanks for this, Mark. Would this provide performance improvements?
Consider the case of POSTing 1 app to a tenant which already has 9 other apps (with per-app API), vs POSTing a tenant with all 10 apps in it (with the old way) - does using the Per-App API mean AS3 only process the 1 additional app, hence can respond quicker?
Definitely. We also plan to focus on performance improvements after the beta. The hope is that POSTing a small update to the API would be less impactful than posting an entire declaration. Look forward to getting lots of amazing feedback on September 12th when AS3-47 is posted.
What about deleting a specific app?
Currently DELETE is not their. Something that could be added. Use POST Declare to remove any apps
How do you manage permissions per app? i only want admin from app team 1 to access API endpoint to make changes for app 1 and not app 2,3,4 etc
Cant because the BIG-IP API doesnt provide the permission. This will be possible on BIG-IP Next using Per APP API.
Promo-SM 😝
@samuelo8976 not sure what you mean by Promo-SM