Summary
While loading from a remote repo, the current behavior of remote loader load call is, if the version is not set, then try to find it from the default branches, which are ubi7 and ubi8, if it couldn't find it there, then exception will be raised.
But is it possible that a config file is not in the default branches but does exist in a specific branch and the version isn't set? then load won't be able to find it, should we make it load from the non-default branch? It might depend on the concept of 'default branches' and the layout of remote repos.
Issue Type
Current behavior
Desired behavior
Use case
ubipop accepts config file name as an argument and will call load() on it, but ubipop doesn't have an option to specify the version of config file it wants to use.
Additional Information
If you conclude that the current behavior is OK, then an issue in ubipop might need to be filed to make it accept version as an argument.
Summary
While loading from a remote repo, the current behavior of remote loader load call is, if the version is not set, then try to find it from the default branches, which are ubi7 and ubi8, if it couldn't find it there, then exception will be raised.
But is it possible that a config file is not in the default branches but does exist in a specific branch and the version isn't set? then load won't be able to find it, should we make it load from the non-default branch? It might depend on the concept of 'default branches' and the layout of remote repos.
Issue Type
Current behavior
Desired behavior
Use case
ubipop accepts config file name as an argument and will call load() on it, but ubipop doesn't have an option to specify the version of config file it wants to use.
Additional Information
If you conclude that the current behavior is OK, then an issue in ubipop might need to be filed to make it accept version as an argument.