tjeerddie

hey, I found a good example for the token validation that also uses the `on behalf of` flow to let the API communicate with the Microsoft API's. https://github.com/Azure-Samples/ms-identity-python-on-behalf-of would be...

details aside, It would be cool to have. We have worked around this by using form validation and workflow steps to first check if a resource type has the correct...

This is already possible with GraphQL by using this query: ``` query IntrospectionQuery { __schema { types { kind name enumValues { name } } } } ``` It gives...

Another similar option is getting the types of the resource, which could also be done at the same time as fetching the resource (also without being able to filter types):...

We do need the ProductModel graphql type because it is necessary for the auto registration of products to resolve correctly. I believe the best approach is to update `ProductModel` to...

I think this can be closed, updated in https://github.com/workfloworchestrator/orchestrator-core/pull/633

This also causes problems for steps that use a union of product models, such as `subscription: ModelActive | ModelProvisioning`, because the value ends up as a dict instead of either...

not sure why the server closes immediately... with the fix for show-schedule, I also changed the store to use orchestrator.db instead of using DB url, which might fix this

I checked the dates between the database and main.py schedule show-schedule, and they match. for example nightly_port: - show schedules: 2025-10-22 00:30:00+00:00 - DB: 1761093000, formats to 2025-10-22 00:30:00+00:00 When...