Renamed global preference file to preference.yaml from config.yaml#1784
Renamed global preference file to preference.yaml from config.yaml#1784openshift-merge-robot merged 1 commit intoredhat-developer:masterfrom girishramnani:rename/global_config_to_preference
Conversation
|
/retest |
cdrage
left a comment
There was a problem hiding this comment.
This LGTM.
Are there any tests you need to fix?
|
/retest |
|
No all the tests should work @cdrage |
|
/retest |
|
@girishramnani We are not doing ensuring the backward compatibility after all? |
|
@kadel according to the discussion in the issue, @jorgemoralespou said that having a changelog entry would be enough |
After this commit, the global preference's default name will be preference.yaml instead of config.yaml. As this file is present in the ~/.odo folder it will not colide with the config.yaml if someone chooses to create a component in home dir.
|
@girishramnani can you please add how will the Release change entry look like?
I know, I was saying originally the same :-) I'm just making sure that this is what you want to do as you had good arguments why we should try to do it as nonbreaking change. |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kadel The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/lgtm |
What is the purpose of this change? What does it change?
The global preference's default name changes to preference.yaml instead of config.yaml. As this file is present in the ~/.odo folder it will not colide with the config.yaml if someone chooses to create a component in home dir.
Was the change discussed in an issue?
fixes #1766
How to test changes?
NOTE - Add this to the ChangeLog as this is a breaking change