Hi Not sure if this is the right place for the question But

Question

Hi Not sure if this is the right place for the question But i am following this tutorial I have successfully reached the step where i create the deployment with this command `prefect deployment build log flow py log flow n log simple q test` which generate the yaml file But it looks slightly different for `infrastructure` where in the tutorial they have ```infrastructure type process env labels name null command python m prefect engine stream output true``` and i have ```infrastructure type process env labels name null command null stream output true block type slug process block type slug process``` And when i run `prefect deployment apply log flow deployment yaml` I get this error ```prefect exceptions PrefectHTTPStatusError Client error 403 Forbidden for url lt prefect domain gt api block types 016c45c9 6346 49c1 a1cb da3021f915b2 Response detail protected block types cannot be updated For more information check An exception occurred ``` Anyone knows what i need to do

jpuris · Answer

Can reproduce the difference in deployment manifest file Have not run into the mentioned `Response detail protected block types cannot be updated ` when applying said manifest though shrug `prefect build` 2 4 2 would generate ```prefect deployment build log flow py log flow n log simple q test``` ``` A complete description of a Prefect Deployment for flow log flow name log simple description null version c2966c5bd40b38928108be01c093c08a The work queue that will handle this deployment s runs work queue name test tags parameters schedule null infra overrides infrastructure type process env labels name null command null stream output true block type slug process block type slug process DO NOT EDIT BELOW THIS LINE flow name log flow manifest path null storage null path Users jp projects test entrypoint log flow py log flow parameter openapi schema title Parameters type object properties required null definitions null``` while prefect 2 0 1 would output ```prefect deployment build log flow py log flow n log simple``` ``` A complete description of a Prefect Deployment for flow log flow name log simple description null version c2966c5bd40b38928108be01c093c08a tags parameters schedule null infra overrides infrastructure type process env labels name null command python m prefect engine stream output true DO NOT EDIT BELOW THIS LINE flow name log flow manifest path null storage null path Users jp projects test entrypoint log flow py log flow parameter openapi schema title Parameters type object properties required null definitions null``` diff ``` diff yaml 6a7 8 gt The work queue that will handle this deployment s runs gt work queue name test 16 19c18 lt command lt python lt m lt prefect engine gt command null 20a20 22 gt block type slug process gt block type slug process gt ``` log flow py ``` cat log flow py from prefect import flow flow def log flow gt None print Hello World if name == main log flow ```

Deepanshu Aggarwal · Answer

i was facing a very similar issue few days back i was using the wrong api url and key please verify it once

jpuris · Answer

logged into cloud or not does not make a difference in my test shrug

Robin Eklund · Answer

Thanks for your response < Deepanshu Aggarwal> the flow gets created so it should be the correct api URL also for creating the flow no key was needed

Robin Eklund · Answer

I didn t mention that but we have deployed Prefect 2 on AWS in EKS

jpuris · Answer

< Robin Eklund> just to be sure are you applying the built deployment yaml to prefect 1 or 2 Are you able to reproduce this locally If so do you have a minimally reproducible example thinking face

Robin Eklund · Answer

i am using the prefect cli `2 4 0` and applying the deployment to prefect 2

Robin Eklund · Answer

seems it is `2 4 2` but i guess the minor version shouldn t matter

Robin Eklund · Answer

I haven t seen this error locally before this test i am doing atm was to deploy a flow to self hosted prefect 2 Let me know if i can provide with any other information or if you would be up for a call

Rob Freedy · Answer

Are you able to run `prefect config view` and double check your api key and api url

Robin Eklund · Answer

```prefect config view PREFECT PROFILE= default PREFECT API URL= lt the prefect domain gt api from profile ```

Robin Eklund · Answer

this is what i have and it seems to be correct but i haven generated any api key

Rob Freedy · Answer

It looks like you may need to create and set an API Key to access blocks that were created in the UI I would recommend looking into this documentation <https docs prefect io ui cloud getting started create an api key>