You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.
User story
Today, Swagger-Promote is expecting, when using a stage, to load the stage environment properties from the relative folder: conf.
But when using Swagger-Promote as a Java-Dependency that might unhandy. Instead, there should be an option to tell Swagger-Promote where conf folder is located.
This can be used for instance when using Swagger-Promote as part of the pipeline using Maven.
The text was updated successfully, but these errors were encountered:
If the new environment variable: SWAGGER_PROMOTE_HOME is set, this folder is used to load environment properties. For that SWAGGER_PROMOTE_HOME must contain the conf folder.
A user can override SWAGGER_PROMOTE_HOME with the new parameter: swaggerPromoteHome
User story
Today, Swagger-Promote is expecting, when using a stage, to load the stage environment properties from the relative folder: conf.
But when using Swagger-Promote as a Java-Dependency that might unhandy. Instead, there should be an option to tell Swagger-Promote where
conf
folder is located.This can be used for instance when using Swagger-Promote as part of the pipeline using Maven.
The text was updated successfully, but these errors were encountered: