As an administrator, I want to use the same configuration file for the different big-data harvest components

nasa-pds-engineering-node / pds-registry-app

(deprecated) See https://github.com/NASA-PDS/registry for new and improved capability.

https://nasa-pds.github.io/registry/

Other

1 stars 1 forks source link

As an administrator, I want to use the same configuration file for the different big-data harvest components #242

Open tloubrieu-jpl opened 2 years ago

tloubrieu-jpl commented 2 years ago

💪 Motivation

...so that I can don't have to edit redundant information

📖 Additional Details

⚖️ Acceptance Criteria

Given When I perform Then I expect

⚙️ Engineering Details

This can be discussed but that would streamline the deployment of the application, especially in the context of the docker-compose orchestration. I believe we can just make the components ignore the properties they don't need for that to work (to be confirmed)

tdddblog commented 2 years ago

Can you be more specific? What components and configuration are you talking about?

tloubrieu-jpl commented 2 years ago

Hi @tdddblog ,

I was thinking of components:

registry-harvest-service
registry-harvest-cli
registry-crawler-service

Thanks,

Thomas

jordanpadams commented 2 years ago

@tloubrieu-jpl I agree it would be nice to combine all these configs, but I don't think we will be able to get this in for B12.1. let's re-evaluate priority for next build