Rajvir Jhawar
06/29/2022, 11:17 PMJenny
06/30/2022, 2:01 AMRajvir Jhawar
06/30/2022, 2:13 AMprefect deployment inspect <deployment_name>
You get the following:
{
'id': '2262a77b-aa71-4df5-9a62-0498133b1027',
'created': '2022-06-29T22:41:50.818174+00:00',
'updated': '2022-06-29T23:40:41.666274+00:00',
'name': 'k8s-example',
'flow_id': '88fcc52b-c264-493f-a1d3-96df1be7e110',
'flow_data': {
'encoding': 'blockstorage',
'blob': '{"data": "\\"ae1f6efd-f3e8-47ce-b22c-52fb240a1287\\"",
"block_document_id": "d568bd1a-0254-4a2d-8632-b8d5a5a38ada"}'
},
'schedule': None,
'is_schedule_active': True,
'parameters': {},
'tags': [],
'flow_runner': {
'type': 'kubernetes',
'config': {
'env': {},
'job': {
'kind': 'Job',
'spec': {
'template': {
'spec': {
'containers': [
{'env': [], 'name': 'prefect-job'}
]
}
}
},
'metadata': {'labels': {}},
'apiVersion': 'batch/v1'
},
'image': 'prefecthq/prefect:2.0b7-python3.9',
'labels': {},
'namespace': 'default',
'stream_output': True,
'customizations': [
{
'op': 'add',
'path':
'/spec/template/spec/containers/0/resources/limits/-',
'value': {'cpu': '500m'}
}
],
'restart_policy': None,
'image_pull_policy': None,
'service_account_name': None,
'job_watch_timeout_seconds': 5,
'pod_watch_timeout_seconds': 5
}
}
}
I would have expected the UI to have the same information. For instance its missing:
1. updated time --> useful to know if your changes got pushed to the cloud
2. specific flow runner details (in the UI you only add the type)
3. more specific flow data details
It be nice if the UI would mirror the data in CLI so you don't have to switch back and forth between the two.Jenny
06/30/2022, 2:20 AMBring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.
Powered by