Skip to content
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.

[Feature] Load Stage-Environment properties from given folder #249

Closed
cwiechmann opened this issue Mar 26, 2020 · 2 comments
Closed

[Feature] Load Stage-Environment properties from given folder #249

cwiechmann opened this issue Mar 26, 2020 · 2 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@cwiechmann
Copy link

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.

@cwiechmann cwiechmann added the enhancement New feature or request label Mar 26, 2020
@cwiechmann cwiechmann self-assigned this Mar 26, 2020
@cwiechmann cwiechmann added this to the 1.6.6 milestone Mar 26, 2020
cwiechmann pushed a commit that referenced this issue Mar 26, 2020
a given folder.

Loaded environment properties from file: C:/temp/sampleConfigs\env.api-env.properties
@cwiechmann
Copy link
Author

cwiechmann commented Mar 26, 2020

With version 1.6.6 Swagger-Promote allows to load environment properties from a given SWAGGER_PROMOTE_HOME directory.

cwiechmann pushed a commit that referenced this issue Mar 27, 2020
containing a conf directory that is  used to load environment properties.
@cwiechmann cwiechmann reopened this Mar 27, 2020
@cwiechmann
Copy link
Author

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant