cli
cli copied to clipboard
APIE-571 - update for default compute pool
Release Notes
Breaking Changes
- PLACEHOLDER
New Features
- Add support for flink default compute pool
Bug Fixes
- PLACEHOLDER
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. - [x] I have put checkmarks below confirming that the feature associated with this PR is enabled in:
- [x] Confluent Cloud prod
- [ ] Confluent Cloud stag
- [ ] Confluent Platform
- [ ] Check this box if the feature is enabled for certain organizations only
What
This will allow user to submit statement without an explicitly specified compute pool (CP). Instead, backend will provision a “default” compute pool (DCP) that is created and managed on the user’s behalf.
Blast Radius
Flink statement create and flink compute pool commands could be affected for existing as well as new behaviour.
References
https://confluentinc.atlassian.net/browse/APIE-571
Test & Review
Added extensive integration tests
Manual Testing:
Statement create without compute pool:
Starting flink shell without compute pool:
Without this change:
CLI Flag --default-pool
Default Compute Pool and Default Max CFU:
: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.
Analysis Details
3 Issues
0 Bugs
0 Vulnerabilities
3 Code Smells
Coverage and Duplications
85.10% Coverage (78.20% Estimated after merge)
No duplication information (0.00% Estimated after merge)
Project ID: cli
Quality Gate passed
Issues
7 New issues
1 Fixed issue
0 Accepted issues
Measures
0 Security Hotspots
85.1% Coverage on New Code
1.0% Duplication on New Code