Breaking: remove dataset link - #368
Conversation
There was a problem hiding this comment.
Pull request overview
This PR removes the deprecated cloudos datasets link CLI subcommand (and its documentation) and bumps the CLI patch version accordingly, steering users toward cloudos interactive-session link / --link alternatives.
Changes:
- Removed the
cloudos datasets linkcommand implementation from the datasets CLI module. - Updated README to remove
datasets linkdocumentation and point users to the supported linking commands. - Bumped version to
2.94.2and added release notes to the changelog.
Reviewed changes
Copilot reviewed 7 out of 7 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| README.md | Removes datasets link documentation and replaces it with guidance to interactive-session link / --link. |
| cloudos_cli/datasets/cli.py | Deletes the datasets link command implementation (and related import). |
| cloudos_cli/_version.py | Bumps package version to 2.94.2. |
| CHANGELOG.md | Adds a v2.94.2 entry describing removal of datasets link. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
|
@danielboloc thanks for the comment! I have updated the behaviour |
|
Bugbot is not enabled for this team, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
|
Bugbot is not enabled for this team, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
danielboloc
left a comment
There was a problem hiding this comment.
Thanks @l-mansouri LGTM


Overview
This PR removes the datasets link command and removes support for the v1 linking endpoint that got deprecated.
JIRA
LP-112583
Changes
Removes
cloudos datasets linkcommand and support for a deprecated endpointAcceptance Criteria
Scenario 1: Command is no longer available
Scenario 2: User is guided to the supported alternatives
Scenario 3: Other datasets subcommands remain functional
Scenario 4: Help text and docs are clean