Hi,

I am trying to understand the use case and underlaying process of "Application lifecycle" option.

When we enable the "Application Lifecycle" on the catalog. we see that when App is created at first , it shows as development and the goes approval process. And once approved the status becomes Production.

but I am not able to follow what is the use case for this to be used. 

Hiya

Some customers might have different backend endpoints they want to call for "development" vs "production", where those states refer to the Application Developer (the consumer).

For example allowing the application developer to test their consuming application against mock data before they request upgrade to production. The Application Lifecycle feature sets some context variables in the API Assembly so you can then do whatever routing or logic that you want accordingly. E.g. you could use the mock policy to return templated data if it is a development app, and only actually invoke the real backend if is a production app.

------------------------------
Chris Dudley

Original Message:
Sent: Thu April 04, 2024 07:43 AM
From: Syed Imtiyaz Alam
Subject: Application Lifecycle

Hi,

I am trying to understand the use case and underlaying process of "Application lifecycle" option.

When we enable the "Application Lifecycle" on the catalog. we see that when App is created at first , it shows as development and the goes approval process. And once approved the status becomes Production.

but I am not able to follow what is the use case for this to be used. 

------------------------------
Syed Imtiyaz Alam
------------------------------

Thank you Chris, this does makes sense.

this is available now: client.app.lifecycle-state

------------------------------
Syed Imtiyaz Alam

Original Message:
Sent: Fri April 05, 2024 05:31 AM
From: Chris Dudley
Subject: Application Lifecycle

Hiya

Some customers might have different backend endpoints they want to call for "development" vs "production", where those states refer to the Application Developer (the consumer).

For example allowing the application developer to test their consuming application against mock data before they request upgrade to production. The Application Lifecycle feature sets some context variables in the API Assembly so you can then do whatever routing or logic that you want accordingly. E.g. you could use the mock policy to return templated data if it is a development app, and only actually invoke the real backend if is a production app.

------------------------------
Chris Dudley

Original Message:
Sent: Thu April 04, 2024 07:43 AM
From: Syed Imtiyaz Alam
Subject: Application Lifecycle

Hi,

I am trying to understand the use case and underlaying process of "Application lifecycle" option.

When we enable the "Application Lifecycle" on the catalog. we see that when App is created at first , it shows as development and the goes approval process. And once approved the status becomes Production.

but I am not able to follow what is the use case for this to be used. 

------------------------------
Syed Imtiyaz Alam
------------------------------