[New Feature]: Improve the OGC registration process

[LucaCinquini]

Currently, once a DAG is registered via the OGC registration method, if the developer wants to update it, they need to first unregister it, then register it again. We want to change the implementation such that once a DAG is registered, the registration method can be executed again to push updates.

As part of this ticket, make sure that the OGC registration method respects the "enabled/disabled" status of a DAG (see the "db_cleanup_dag" DAG which is disabled by default, which then can enabled automatically at registration).

[nikki-t]

The OGC API - Processes - Part 2: Deploy, Replace, Undeploy indicates the following:

A server that implements the DRU Requirements Class provides the ability to dynamically deploy, replace and undeploy processes.

The HTTP POST method is used to deploy a new process to the API.

The HTTP PUT method is used to replace the definition of a previously deployed processes that are accessible via the Processes API endpoint.

Finally, the HTTP DELETE method is used to undeploy a previously deployed process that is accessible via the Processes API endpoint.

I think the goal of the specification is for the user to use the HTTP PUT method to replace (or update) existing processes and I am wondering that if we change this behavior will the API no longer be OGC compliant?

I would still like to investigate how to make this change and it looks like this is the function that raises an exception if the process already exists and this file contains the deploy, replace, and undeploy functions.

I think it might make sense to remove the lines that raise an HTTPException and returns a 409.

[LucaCinquini]

Hi Nikki, if you can implement the PUT method then it would be great Thanks, Luca On May 21, 2025, at 9:20 PM, Nikki Tebaldi ***@***.***> wrote:  [https://avatars.githubusercontent.com/u/17799906?s=20&v=4]nikki-t left a comment (unity-sds/unity-sps#408)<https://urldefense.us/v3/__https://github.com/unity-sds/unity-sps/issues/408*issuecomment-2898983745__;Iw!!PvBDto6Hs4WbVuu7!Ke_tnbDia9C8lzokhbykT8wv3pFQrAH1d5pAsYv4w3ciaQ87-t5kelENhDc5wZYKJrdWLaifo7dPEVaiFDCC6KGSAQT61otN7Q$> The OGC API - Processes - Part 2: Deploy, Replace, Undeploy<https://urldefense.us/v3/__https://github.com/unity-sds/unity-sps-ogc-processes-api/blob/a1d8b707fe4f713f4ee7d8a592d36221cccad49d/app/src/openapi_server/impl/dru_api.py*L19__;Iw!!PvBDto6Hs4WbVuu7!Ke_tnbDia9C8lzokhbykT8wv3pFQrAH1d5pAsYv4w3ciaQ87-t5kelENhDc5wZYKJrdWLaifo7dPEVaiFDCC6KGSAQR4QS0CaA$> indicates the following: A server that implements the DRU Requirements Class provides the ability to dynamically deploy, replace and undeploy processes. The HTTP POST method is used to deploy a new process to the API. The HTTP PUT method is used to replace the definition of a previously deployed processes that are accessible via the Processes API endpoint. Finally, the HTTP DELETE method is used to undeploy a previously deployed process that is accessible via the Processes API endpoint. I think the goal of the specification is for the user to use the HTTP PUT method to replace (or update) existing processes and I am wondering that if we change this behavior will the API no longer be OGC compliant? I would still like to investigate how to make this change and it looks like this is the function<https://urldefense.us/v3/__https://github.com/unity-sds/unity-sps-ogc-processes-api/blob/a1d8b707fe4f713f4ee7d8a592d36221cccad49d/app/src/openapi_server/impl/dru_api.py*L19__;Iw!!PvBDto6Hs4WbVuu7!Ke_tnbDia9C8lzokhbykT8wv3pFQrAH1d5pAsYv4w3ciaQ87-t5kelENhDc5wZYKJrdWLaifo7dPEVaiFDCC6KGSAQR4QS0CaA$> that raises an exception if the process already exists and this file<https://urldefense.us/v3/__https://github.com/unity-sds/unity-sps-ogc-processes-api/blob/develop/app/src/openapi_server/impl/dru_api.py__;!!PvBDto6Hs4WbVuu7!Ke_tnbDia9C8lzokhbykT8wv3pFQrAH1d5pAsYv4w3ciaQ87-t5kelENhDc5wZYKJrdWLaifo7dPEVaiFDCC6KGSAQRKqKiXiQ$> contains the deploy, replace, and undeploy functions. I think it might make sense to remove the lines that raise an HTTPException and returns a 409. — Reply to this email directly, view it on GitHub<https://urldefense.us/v3/__https://github.com/unity-sds/unity-sps/issues/408*issuecomment-2898983745__;Iw!!PvBDto6Hs4WbVuu7!Ke_tnbDia9C8lzokhbykT8wv3pFQrAH1d5pAsYv4w3ciaQ87-t5kelENhDc5wZYKJrdWLaifo7dPEVaiFDCC6KGSAQT61otN7Q$>, or unsubscribe<https://urldefense.us/v3/__https://github.com/notifications/unsubscribe-auth/AAE3RA3TDFPOIVWEIKGWRI327TGYXAVCNFSM6AAAAAB42XW6D2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQOJYHE4DGNZUGU__;!!PvBDto6Hs4WbVuu7!Ke_tnbDia9C8lzokhbykT8wv3pFQrAH1d5pAsYv4w3ciaQ87-t5kelENhDc5wZYKJrdWLaifo7dPEVaiFDCC6KGSAQQcsYpedA$>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[nikki-t]

@LucaCinquini - It looks like the PUT method may already be implemented: https://github.com/unity-sds/unity-sps-ogc-processes-api/blob/a1d8b707fe4f713f4ee7d8a592d36221cccad49d/app/src/openapi_server/impl/dru_api.py#L139-L200

I tested it to make sure it works and I get the following error message back:

{
    "detail": "Method Not Allowed"
}

Which makes me think the method may not be defined for the API Gateway but I will look further and see if I can figure out the origin of the error message.

[nikki-t]

I had the wrong API call which produced the above error message. Instead this is what I get when I try a PUT request to replace a DAG:

{
    "detail": "400 Client Error: BAD REQUEST for url: http://airflow-webserver.sps.svc.cluster.local:8080/api/v1/dags/cwl_dag/dagRuns"
}

Which is similar to what I see when I run the API locally and make queries against it so I think I can debug locally and then apply the changes to my deployment.

[nikki-t]

PR: unity-sds/unity-sps-ogc-processes-api#17

[nikki-t]

I updated the GitBook docs: https://app.gitbook.com/o/xZRqGQeQXJ0RP4VMj7Lq/s/UMIRhLdbRQTvMWop8Il9/developer-docs[…]velopers-guide/tutorial-using-the-ogc-processes-api-with-curl

And staged updates for Cognito tokens and the update process in the Python notebook: https://github.com/unity-sds/unity-monorepo/blob/408-ogc-registration-replace/libs/unity-py/notebooks/ogc_notebook.ipynb

But am holding off until we finalize the use of tokens in the unity-py client before creating a PR