feat: utilize ProjectStages for extending configuration #1

New issue

Open

opened 2020-06-03 03:22:08 +01:00 by SethFalco · 0 comments

SethFalco commented 2020-06-03 03:22:08 +01:00 (Migrated from gitlab.com)

Copy link

We should support multiple config files on initialization, instead of just the specified name.

For example, if the ProjectStage is production then we should read application.yml and then append or replace values with what's found in application-production.yml if the file exists, or if the ProjectStage is test then application-test.yml.

We should support multiple config files on initialization, instead of just the specified name. For example, if the `ProjectStage` is `production` then we should read `application.yml` and then append or replace values with what's found in `application-production.yml` if the file exists, or if the `ProjectStage` is `test` then `application-test.yml`.

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

main

1.3.0

1.2.1

1.2.0

1.1.1

1.1.0

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

SethFalco/yaml4deltaspike#1

No description provided.