Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move corrections to static file and GitHub repo? #75

Open
retzkek opened this issue Aug 14, 2020 · 2 comments
Open

Move corrections to static file and GitHub repo? #75

retzkek opened this issue Aug 14, 2020 · 2 comments

Comments

@retzkek
Copy link
Collaborator

retzkek commented Aug 14, 2020

I've been finding myself regretting the early decision to put VO and project name corrections into Elasticsearch. I think having them in static files in a repo, similar to the topology information, would be more maintainable, and allow changes via PR instead of ticket. @djw8605 @zvada what do you think?

@djw8605
Copy link
Member

djw8605 commented Aug 14, 2020

Static files would be fine for me. I agree it may be easier to maintain. Have you thought about the implementation of this? I presume it would be very similar to reading OIM information.

@retzkek
Copy link
Collaborator Author

retzkek commented Aug 14, 2020

I presume it would be very similar to reading OIM information.

Yeah, that's what I'm thinking.

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

No branches or pull requests

2 participants