https://prefect.io logo
Join Slack
Powered by
Hi, my Deployments in Prefect Cloud UI are not dis...
# prefect-ui
j
Hi, my Deployments in Prefect Cloud UI are not displaying the deployment parameters. The deployment for my flow always says 0 parameters. However, when I run 
prefect deployment inspect flow_name/deployment_name
for my deployment, I can see the parameters in the returned JSON. Additionally, this means that I can’t override the Deployment parameters for ad-hoc runs of my flows. Is this an expected behaviour in any of the Prefect Cloud UIs?
c
Hey Jiri - can you share the JSON payload for your parameters? I've seen this happen before when the parameter specification is not in a proper OpenAPI compliant format
j
Hi @Chris White, I’m not sure how to provide that - we create the Deployments via the 
Deployment
python object, then 
Deployment.apply(upload=False)
. The parameters are very simple, such as 
{foo: 3, bar: 4}
c
I mean copy / paste it from the CLI command 
prefect deployment inspect flow_name/deployment_name
j
gotcha
Copy code
{
    'id': 'fa6b0dc1-6f46-42fb-a03b-6160d6b6b906',
    'created': '2023-03-22T13:50:43.993576+00:00',
    'updated': '2023-04-11T16:20:31.317039+00:00',
    'name': 'uat',
    'version': None,
    'description': None,
    'flow_id': '1be388ed-7f63-45f9-8347-72460a38749d',
    'schedule': None,
    'is_schedule_active': True,
    'infra_overrides': {'cpu': '256', 'image': 'REDACTED', 'memory': '512', 'cloudwatch_logs_options': {'awslogs-group': 'data/prefect2', 'awslogs-region': 'eu-west-2', 'awslogs-stream-prefix': 'tools/always_fails.py'}},
    'parameters': {'bar': 4, 'foo': 3},
    'tags': [],
    'work_queue_name': 'uat',
    'parameter_openapi_schema': {'type': 'object', 'title': 'Parameters', 'properties': {}},
    'path': '/src_prefect2/flows/tools',
    'entrypoint': 'always_fails.py:flow',
    'manifest_path': None,
    'storage_document_id': None,
    'infrastructure_document_id': '5941200f-8d4d-4a40-82dc-0f7dcd2c9e62',
    'created_by': {'id': '1ae28e4b-ac0c-432b-9e38-e5d7ffee2566', 'type': 'USER', 'display_value': 'REDACTED'},
    'updated_by': {'id': '1ae28e4b-ac0c-432b-9e38-e5d7ffee2566', 'type': 'USER', 'display_value': 'REDACTED'},
    'work_pool_name': 'uat',
    'infrastructure': {
        'type': 'ecs-task',
        'env': {},
        'labels': {},
        'name': None,
        'command': None,
        'aws_credentials': {'aws_access_key_id': None, 'aws_secret_access_key': None, 'aws_session_token': None, 'profile_name': None, 'region_name': None, 'aws_client_parameters': {'api_version': None, 'use_ssl': True, 'verify': True, 'verify_cert_path': None, 'endpoint_url': None, 'config': None}, 'block_type_slug': 'aws-credentials'},
        'task_definition_arn': None,
        'task_definition': None,
        'family': None,
        'image': 'REDACTED',
        'auto_deregister_task_definition': True,
        'cpu': 1024,
        'memory': 2048,
        'execution_role_arn': 'REDACTED',
        'configure_cloudwatch_logs': True,
        'cloudwatch_logs_options': {'awslogs-group': 'data/prefect2', 'awslogs-region': 'eu-west-2', 'awslogs-stream-prefix': 'flow'},
        'stream_output': None,
        'launch_type': 'FARGATE',
        'vpc_id': 'REDACTED',
        'cluster': 'REDACTED',
        'task_role_arn': 'REDACTED',
        'task_customizations': [{'op': 'replace', 'path': 'REDACTED', 'value': 'DISABLED'}, {'op': 'add', 'path': 'REDACTED', 'value': ['REDACTED']}],
        'task_start_timeout_seconds': 120,
        'task_watch_poll_interval': 5.0,
        'block_type_slug': 'ecs-task'
    }
}
I had to redact a bunch of information, but this is the gist
Also - I raised an issue here to avoid duplication https://github.com/PrefectHQ/prefect/issues/9240
c
OK great, I'll respond there if that's OK
👍 1
2 Views
Open in Slack
PreviousNext
Powered by