Support for import of servers defined in Open API spec

[Kiran-B]

Open API spec allows definition of multiple servers. The import of such specs are successful. But Postman appears to choose/use the first server URL.

Requested behavior:

• Server URL and protocol translates to two variables. Approach may extend to other server variables as defined in spec.
• Multiple environments are automatically created. one-each for the server definition. The environment defines the values of server variables (like URL and PROTOCOL) as defined in the open api spec.

Multiple server URLs are often used to target multiple deployment environment like Dev, Stage and Prod. Hence the suggestion to creation Postman Environment for each server configuration.

[jziggas]

I also have a use case of test, stage, and prod server urls. As well as a few product team urls. Importing the OpenApi 3.0.3 document into Postman only generates the first server url defined in the document. This is not useful to teams because individuals will have to manually enter the additional servers urls each time the document is updated, which will lead to individuals saving their own Postman json files rather than importing from the common source of truth.

[fosternb10]

Added in 2018 but still commenting in 2022. Does an ETA exist for this feature?

[AlexKotsc]

Possible fix that solves my use case; I'm not sure how to contribute to this project directly, so I've made changes on a fork.

AlexKotsc@36c959f

[lougeo]

I also have this requirement, and would like to see this implemented.

[noryson]

Please, this implementation is needed. I've had to manually copy the other server urls and associated data into postman environment variable every time. Not nice at all :(

[dgmora]

This is a quite necessary for those who generate open API documentation first and then import it to postman. Is there some reason not to implement it? 😢

[glebignatieff]

+1, this would be very beneficial for our team

[vordimous]

+1, not having this will be pushing us to use a different solution.

[MarioAquino-MAQU]

Same issue here. We have a global server definition. But some paths need their own server definition because we have webservices running on different ports. These server definitions are currently not respected.