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

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

Open
tloubrieu-jpl opened this issue Jan 27, 2022 · 3 comments

Comments

@tloubrieu-jpl
Copy link
Contributor

💪 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
Copy link
Contributor

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

@tloubrieu-jpl
Copy link
Contributor Author

Hi @tdddblog ,

I was thinking of components:

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

Thanks,

Thomas

@jordanpadams
Copy link
Contributor

@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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants