[CLI-3498] Custom SMTs support for Managed Connect - CLI
Release Notes
New Features
- Add
confluent connect artifact [create | describe | list | delete]command for Custom SMTs (Single Message Transform) support to facilitate customer adoption of fully-managed connectors
Checklist
- [x] I have successfully built and used a custom CLI binary, without linter issues from this PR.
- [x] I have clearly specified in the
Whatsection below whether this PR applies to Confluent Cloud, Confluent Platform, or both. - [x] I have verified this PR in Confluent Cloud pre-prod or production environment, if applicable.
- [ ] I have verified this PR in Confluent Platform on-premises environment, if applicable.
- [x] I have attached manual CLI verification results or screenshots in the
Test & Reviewsection below. - [x] I have added appropriate CLI integration or unit tests for any new or updated commands and functionality.
- [x] I confirm that this PR introduces no breaking changes or backward compatibility issues.
- [x] I have indicated the potential customer impact if something goes wrong in the
Blast Radiussection below. - [ ] I have put checkmarks below confirming that the feature associated with this PR is enabled in:
- [ ] Confluent Cloud prod
- [x] Confluent Cloud stag
- [ ] Confluent Platform
- [ ] Check this box if the feature is enabled for certain organizations only
What
Add confluent connect artifact command to support Custom SMTs. Adding Custom SMT (Single Message Transform) Support is part of the Seamless Connector Migrations initiative, and it helps to drive fully-managed connector adoption, with the initiative of converting part of the over 800+ Confluent Cloud customers currently self-managing connectors over to using fully-managed connectors.
This is for Confluent Cloud resource.
Blast Radius
None. This is an additive change, so no existing commands should be affected.
References
Test & Review
:tada: All Contributor License Agreements have been signed. Ready to merge.
Please push an empty commit if you would like to re-run the checks to verify CLA status for all contributors.
Manual testing is blocked due to some additional backend requirement changes and currently awaiting the SMT team to update the SDK and enable feature in staging.
Another comment, on the release note:
command to support Custom SMTs
We should write out the full name so users know what SMT means. Also, is Custom SMT the final user facing name that the product team is going with?
Analysis Details
3 Issues
-
0 Bugs
-
0 Vulnerabilities
-
3 Code Smells
Coverage and Duplications
-
90.60% Coverage (76.80% Estimated after merge)
-
No duplication information (0.00% Estimated after merge)
Project ID: cli
Analysis Details
3 Issues
-
0 Bugs
-
0 Vulnerabilities
-
3 Code Smells
Coverage and Duplications
-
90.20% Coverage (76.80% Estimated after merge)
-
No duplication information (0.00% Estimated after merge)
Project ID: cli
Analysis Details
3 Issues
-
0 Bugs
-
0 Vulnerabilities
-
3 Code Smells
Coverage and Duplications
-
90.20% Coverage (76.80% Estimated after merge)
-
No duplication information (0.00% Estimated after merge)
Project ID: cli
Analysis Details
3 Issues
-
0 Bugs
-
0 Vulnerabilities
-
3 Code Smells
Coverage and Duplications
-
90.20% Coverage (77.00% Estimated after merge)
-
No duplication information (0.00% Estimated after merge)
Project ID: cli
Analysis Details
3 Issues
-
0 Bugs
-
0 Vulnerabilities
-
3 Code Smells
Coverage and Duplications
-
90.30% Coverage (77.00% Estimated after merge)
-
No duplication information (0.00% Estimated after merge)
Project ID: cli