import requests
url = "https://platform.ankra.app/org/applications/{application_id}/launch-plan"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text)const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://platform.ankra.app/org/applications/{application_id}/launch-plan', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));curl --request GET \
--url https://platform.ankra.app/org/applications/{application_id}/launch-plan \
--header 'Authorization: Bearer <token>'{
"application_id": "<string>",
"status": "planned",
"commit_sha": "<string>",
"analysed_at": "2023-11-07T05:31:56Z",
"contract_schema_version": "<string>",
"plan": {},
"decision_count": 123
}{
"detail": "<string>"
}{
"detail": [
{
"loc": [
"<string>"
],
"msg": "<string>",
"type": "<string>"
}
]
}Get an application's Launch Plan (browser session)
The Launch Plan for the application (ankra-bjkszh.2, ankra-bjkszh.16), resolved on read from the App Contract of an analysed commit: per external service its lock-in tier with the reason and evidence, the default choice (bring your own, Ankra open source in the cluster, off, a portability PR, or staying at the vendor) and the alternatives; where each environment variable’s value comes from; the migration step, port, IP family and exposure; and the decisions only a person can make. Cluster facts are not read yet and say unknown. The latest analysed commit by default; commit_sha names one. Requires applications.read.
import requests
url = "https://platform.ankra.app/org/applications/{application_id}/launch-plan"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text)const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://platform.ankra.app/org/applications/{application_id}/launch-plan', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));curl --request GET \
--url https://platform.ankra.app/org/applications/{application_id}/launch-plan \
--header 'Authorization: Bearer <token>'{
"application_id": "<string>",
"status": "planned",
"commit_sha": "<string>",
"analysed_at": "2023-11-07T05:31:56Z",
"contract_schema_version": "<string>",
"plan": {},
"decision_count": 123
}{
"detail": "<string>"
}{
"detail": [
{
"loc": [
"<string>"
],
"msg": "<string>",
"type": "<string>"
}
]
}Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Query Parameters
The analysed commit whose plan to resolve; without it, the most recently analysed one.
^[0-9a-f]{7,64}$Response
The resolved plan, or its status when there is nothing to plan from
The Launch Plan (schema ankra.launch-plan/v1, enginekit/launchplan) resolved on read from an analysed commit's App Contract. plan and decision_count are null unless status is planned: not-extracted means no contract has been stored yet, unsupported-contract that the stored contract's schema version is not one this resolver reads.
planned, not-extracted, unsupported-contract The plan document: one entry per dependency with its lock-in tier (drop-in, adapter, re-platform or unknown), reason and evidence, the chosen option (bring-your-own, ankra-open-source, off, needs-portability-pr or stays-at-vendor) and the alternatives; components, environment bindings, migrations, network, exposure, storage, cluster facts, findings and the decisions left to a person.