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

Convert the current solo.config to be stored as YAML instead of JSON #592

Closed
Tracked by #47
jeromy-cannon opened this issue Sep 17, 2024 · 1 comment · Fixed by #609
Closed
Tracked by #47

Convert the current solo.config to be stored as YAML instead of JSON #592

jeromy-cannon opened this issue Sep 17, 2024 · 1 comment · Fixed by #609
Assignees
Labels
HashSphere Requirement P1 High priority issue. Required to be completed in the assigned milestone. released

Comments

@jeromy-cannon
Copy link
Contributor

jeromy-cannon commented Sep 17, 2024

The current solo config is stored as JSON, by defaults as ~/.solo/solo.config. This is to make the necessary changes so that it is stored instead as ~/.solo/solo.yaml.

NOTE: 'js-yaml' examples are in profile-manager.mjs

@github-project-automation github-project-automation bot moved this to 🆕 New in Solo Sep 17, 2024
@jeromy-cannon jeromy-cannon moved this from 🆕 New to 🔖 Ready in Solo Sep 17, 2024
@jeromy-cannon jeromy-cannon added P1 High priority issue. Required to be completed in the assigned milestone. HashSphere Requirement labels Sep 17, 2024
@jeromy-cannon jeromy-cannon moved this from 🔖 Ready to 👀 In review in Solo Sep 30, 2024
@github-project-automation github-project-automation bot moved this from 👀 In review to ✅ Done in Solo Sep 30, 2024
@swirlds-automation
Copy link
Contributor

🎉 This issue has been resolved in version 0.31.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
HashSphere Requirement P1 High priority issue. Required to be completed in the assigned milestone. released
Projects
Status: ✅ Done
Development

Successfully merging a pull request may close this issue.

3 participants