-
Notifications
You must be signed in to change notification settings - Fork 14
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
Include definitions from GitHub repo #265
Include definitions from GitHub repo #265
Conversation
Seems like the cloning of the common-definitions repo only worked locally because of my ssh keys. Working on a fix. |
The implementation looks good, thanks! But I still think that the configuration would be more elegant and future-proof if we do: repository:
common-definitions:
git: git@github.com:IAMconsortium/common-definitions.git
hash: # optional
release: # optional
region:
repository: common-definitions
path: # optional, defaults to `definitions / regions`
variable:
repository: common-definitions
path: # optional, defaults to `definitions / variable` This would make the repository_name explicit and customizable. And the |
Agreed, I'll change it that way. |
Update@danielhuppmann I have updated repository:
common-definitions:
url: https://github.com/IAMconsortium/common-definitions
region:
repository: common-definitions
country: true
variable:
repository: common-definitions
repository_definition_path: definitions / variable I changed your I've also, according to your suggestion moved the repository fetching into the constructor of In addition I've extended the use of external repos from just region to any dimension. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very nice! A few suggestions for alternative keyword names, but good to be merged either way...
Co-authored-by: Daniel Huppmann <dh@dergelbesalon.at>
First version of the external repo fetching feature.
How to use
In the
definitions
folder of a project place a file called definitions with the following content:the
hash
andrelease
attributes are both optional.If neither is given, the last version of the main branch is used.
They are also mutually exclusive. If both are given an error is raised.
Implementation details
The repo fetching logic is implemented as follows: