abeermalik
New Contributor
Joined 2 years ago
User Profile
User Widgets
Contributions
Re: passing url as variable to a swagger specification 2 file converts the double slash to 1 slash
It looks like the issue is occurring because of the URL formatting in your Terraform configuration. The URL is being passed with an extra slash when you specify it in the template. To resolve this issue, you can make sure that the URL is correctly formatted in the Terraform template. Here's how you can fix it: 1. Update your Terraform template to format the URL correctly. You can use the `format` function to ensure that the URL is correctly formatted download vsco mod: ```hcl openapi_documents { document { path = "spec.yaml" contents = filebase64(templatefile("apigateway/openapi2-runner.tftplt", { myUrl = format("https://%s", var.CrSrvApp) })) } } ``` In this example, the `format` function is used to add "https://" before the URL specified in `var.CrSrvApp`. 2. Ensure that the `CrSrvApp` variable does not include "https://" since it is added in the Terraform template. By making these changes, you should pass a correctly formatted URL to your Swagger specification, and the issue with double slashes should be resolved.169Views0likes0CommentsRe: yaml resolved
To ensure that your Swagger definition includes "nullable: true" for objects when exporting it as "YAML Resolved" from SwaggerHub, you can follow these steps: 1. Open your Swagger definition in SwaggerHub. 2. Locate the objects or properties where you want to set "nullable: true." 3. Edit the Swagger definition, and for each object or property, explicitly set "nullable: true." For example: ```yaml properties: someProperty: type: string nullable: true ``` 4. Save your changes. 5. Export the API as "YAML Resolved" again. By manually setting "nullable: true" for the objects or properties in your Swagger definition, you ensure that it is included in the exported YAML file as you intended. This should address the issue you described.245Views0likes0Comments