feat(msk): support Express brokers#34741
Conversation
✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
badmintoncryer
left a comment
There was a problem hiding this comment.
Thank you for your contribution!
I thought it might be a good idea to add a validation to ensure that the Kafka version is 3.6 or higher, but it also feels a bit excessive.
I’d appreciate it if you could discuss with the maintainer.
|
@mazyu36 Cloud you please update PR title? It results updating PR labels. |
kumsmrit
left a comment
There was a problem hiding this comment.
Thank you for your contribution. I have added some review comments.
| * | ||
| * @default false | ||
| */ | ||
| readonly express?: boolean; |
There was a problem hiding this comment.
Can we switch from using boolean to enum instead readonly brokerType?: BrokerType; keeping it more future proof ?
enum BrokerType {
STANDARD = 'STANDARD',
EXPRESS = 'EXPRESS'
}
There was a problem hiding this comment.
Thanks.
Added Enum.
| throw new core.ValidationError('EBS volume size should be in the range 1-16384', this); | ||
| } | ||
|
|
||
| if (props.express) { |
There was a problem hiding this comment.
MSK ExpressBroker is supported only on Apache Kafka 3.6 and 3.8; Can we add that validation please.
There was a problem hiding this comment.
Added a validation.
| You can create an MSK cluster with Express Brokers by setting the `express` property to `true`. Express Brokers are a low-cost option for development, testing, and workloads that don't require the high availability guarantees of standard MSK cluster. | ||
| For more information, see [Amazon MSK Express Brokers](https://docs.aws.amazon.com/msk/latest/developerguide/msk-broker-types-express.html). | ||
|
|
||
| **Note:** When using Express Brokers, the following constraints apply: |
There was a problem hiding this comment.
nit: It would also be good to include information about the supported broker sizes
There was a problem hiding this comment.
kumsmrit
left a comment
There was a problem hiding this comment.
Thank you for addressing the comments.
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
|
This pull request has been removed from the queue for the following reason: The merge conditions cannot be satisfied due to failing checks:You may have to fix your CI before adding the pull request to the queue again. |
|
@Mergifyio update |
☑️ Nothing to do, the required conditions are not metDetails
|
Pull request has been modified.
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
|
Comments on closed issues and PRs are hard for our team to see. |
Issue # (if applicable)
Closes #32923.
Reason for this change
To support express brokers.
Description of changes
Add
expressproperty and validations about express limitations.Describe any new or updated permissions being added
N/A
Description of how you validated changes
Add unit tests and an integ test.
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license