No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

There’s a Pulumi resource to define API operations <https://github.com/pulumi/examples/blob/master/azure-ts-api-management/index.ts#L47>

And swagger definition can be imported with <https://github.com/pulumi/pulumi-azure/blob/master/sdk/dotnet/Apimanagement/Api.cs#L183>

```contentFormat - (Required) The format of the content from which the API Definition should be imported. Possible values are: swagger-json, swagger-link-json, wadl-link-json, wadl-xml, wsdl and wsdl-link.

contentValue - (Required) The Content from which the API Definition should be imported. When a content_format of *-link-* is specified this must be a URL, otherwise this must be defined inline.```


I haven't managed to figure out how to do this, the issue is that the swagger file is exposed by an app service that is registered to the api management service, so I need to have the api management load the swagger after the app service is deployed, is this possible? Can I run pulumi scripts post deploy?

And the point of the swagger was too not have to define operations myself but have the api management service register them from a swagger file.

If you could get the swagger file from the app service inside the Pulumi program, you could pass it to API Management and Pulumi would do those in the right sequence.

Honestly, I haven’t done much with API Management, so all this is theory.