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

cannot create component in home directory #1766

Closed
girishramnani opened this issue May 24, 2019 · 5 comments · Fixed by #1784
Closed

cannot create component in home directory #1766

girishramnani opened this issue May 24, 2019 · 5 comments · Fixed by #1784
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/Medium Nice to have issue. Getting it done before priority changes would be great.

Comments

@girishramnani
Copy link
Contributor

As there is a preference file present in the home directory with the name path as the local config file .odo/config.yaml, people cannot create components in their home directory ( which could be something someone does )

@girishramnani
Copy link
Contributor Author

we can consider changing the name of the preference file to .odo/preference.yaml instead to make sure people can create components in home directories

@cdrage
Copy link
Member

cdrage commented May 24, 2019

👍 on this, this would be related to the previous issue I had: #1729

👍 on renaming it to preference.yaml

@amitkrout
Copy link
Contributor

@girishramnani Can you please assign label to it

@girishramnani girishramnani added kind/bug Categorizes issue or PR as related to a bug. state/In Analysis priority/Medium Nice to have issue. Getting it done before priority changes would be great. labels May 27, 2019
@girishramnani
Copy link
Contributor Author

@jorgemoralespou could you please provide you suggestion on these two questions -
1 - renaming the global preference to preference.yaml or preferences.yaml
2 - do we provide automatic migration for users i.e. rename the ~/.odo/config.yaml to the new file?

@jorgemoralespou
Copy link
Contributor

@girishramnani I would go ahead, although bc I honestly hope no one does that, but makes sense.
For question #2 I would just add it to the release notes as I also don't think many people is yet using the preferences.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/Medium Nice to have issue. Getting it done before priority changes would be great.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants