[major] Remove deprecated UDS support #1871
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It has been a long time since UDS EOL (Spring 2024). It is time to remove the role from the collection and clean up any lingering references to UDS and the complexity continuing to have those in our pipelines creates. Any customers still running UDS will need to update to an older catalog using an older version of the collection/CLI, or handle the migration independently.
--uds-firstname,--uds-lastname,--uds-emailto--contact-firstname,--contact-lastname,--contact-email(--uds-firstname,--uds-lastname,--uds-emailare all kept as aliases for the new parameters)--dro-migrationparammas-devops-udstask tomas-devops-droand removes the UDS step from the task (now only supports DRO)Also, updates the build process to support installing the
mas-devopspython package from a matching branch of ibm-mas/python-devops when building the CLI on non-master branch, which means that no longer need to temporarily commit a tgz containing a local build of the package to the repo to test changes across the two repositories.