See API Connect context variables
| Ibm |
remove preview |
|
| API Connect context variables |
| List of IBM API Connect context variables that you can reference when defining default parameter values in an assembly operation, or by using the getContext() function when defining a policy. |
| View this on Ibm > |
|
|
"client.app.lifecycle-state"
------------------------------
Chris Dudley
------------------------------
Original Message:
Sent: Fri April 05, 2024 07:08 PM
From: Syed Imtiyaz Alam
Subject: Application Lifecycle
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