-
Notifications
You must be signed in to change notification settings - Fork 0
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
🎉 release: v8.0.0 #341
🎉 release: v8.0.0 #341
Conversation
Users can now set platform as a product type when they create virtual devices using device manifests. Wrike Ticket: https://www.wrike.com/open.htm?id=1460556021
) When config files are updated to etcd via riocli, it doesn't update the sentinel key that the io-amr stack watches on to figure out config changes. Our ioconfig-syncer implementation does it automatically. In this commit, we ensure that the sentinel key is updated as a part of import. Wrike Task: https://www.wrike.com/open.htm?id=1459385386
When the apply command fails due to a parsing error, it does not mention the file where the error occured. This commit fixes that by raising exceptions with the file name. Wrike Ticket: https://www.wrike.com/open.htm?id=1449838758
There's no way to tell what resources are supported by the explain command. This command prints the list of supported resources. Usage: rio list-examples https://www.wrike.com/open.htm?id=1397379795
Until now, we have been saving the password in plain text in the CLI configuration file. While it makes some things convenient, it compromises security. This commit fixes the issue by no longer storing the password in the configuration file. BREAKING CHANGE: The password is no longer saved in the riocli config.json file. Wrike Ticket: https://www.wrike.com/open.htm?id=1162009098
The list deployment command isn't helpful to know at a glance the actual status of the deployment. Users would have had to inspect the deployments individually to know the errors and even then it won't be helpful enough to derive the actual error. This commit fixes the issue by parsing the error code and printing the error. Wrike Ticket: https://www.wrike.com/open.htm?id=1449503225
Exceptions aren't handled gracefully in the CLI. It's cumbersome to do it at all the places. This fix wraps the entrypoint in a try-except block and gracefully handles the exceptions. You can set the DEBUG=true in order to continue seeing the tracebacks. Wrike Ticket: https://www.wrike.com/open.htm?id=1382438801
The name_to_request_id decorator in device utils tries to find the request id corresponding an uploaded file. It invoke a list call to fetch the files and find out the id. However, list_uploaded_files_for_device SDK method supports filtering by file name. This commit fixes the call to filter with file name to only return the required data. Wrike Ticket: https://www.wrike.com/open.htm?id=1463047318
The apply command provides an overview of how much time it may take and the actions that will be performed during apply. However, the calculation was based on estimates and are incorrect. Similary, the actions are also incorrect at many places and neither do we need it. This commit removes the chunk of code that prints that info. Wrike Ticket: https://www.wrike.com/open.htm?id=1183537395
The organization select command checks whether the currently set organization is already the selected one. It relies on the organization_id in the config. However, there may be a case where the config may not have the organization entry. In such a case, accessing the key without .get() throws a key error. This commit rectifies the issue. Wrike Ticket: https://www.wrike.com/open.htm?id=1464951724
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
🤖 Pull Request Artifacts (#10178986444) 🎉 |
🎉 This PR is included in version 8.0.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Description
This is a release PR.