-
Notifications
You must be signed in to change notification settings - Fork 9.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
r/aws_kinesis_firehose_delivery_stream - Send defaults for BufferIntervalInSeconds and BufferSizeInMBs #26964
r/aws_kinesis_firehose_delivery_stream - Send defaults for BufferIntervalInSeconds and BufferSizeInMBs #26964
Conversation
…rvalInSeconds and BufferSizeInMBs Send default processor parameter values to remove requirement to set both 'BufferSizeInMBs' and 'BufferIntervalInSeconds' even if one is using the default value.
Community NoteVoting for Prioritization
For Submitters
|
@ewbankkit is this being looked at? I'm trying to run the tests to open another PR and this issue is a blocker. PR that is blocked: #28469 |
@mtt88 Were you able to get all tests passing with this? I believe the kinesis firehose testing suite fails due to the dissonance between the resource and default values. |
@ameddin73 - I'm afraid it's been a while since I looked at this - I'll try and find the time over the next few days to review any failing tests. Matt |
@ameddin73 Whilst I've not run the entire test suite, I've run some of the tests which were failing on your branch (
I've not run the failing Elastic Search or Redshift tests yet so it would be helpful if someone has the ability to run the entire test suite against this branch. |
This work has been rolled into #35137. |
…StreamConfig_extendedS3UpdatesSetBufferIntervalNoBufferSize' (hashicorp#26964).
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
When updating the BufferIntervalInSeconds or BufferSizeInMBs processor parameters on a
kinesis_firehose_delivery_stream
, if we wish to change only one of these parameters then we no longer need to set the other to it's 'default' value.Not really a bug but due to requirement by the API to set both of these parameters it will cause an annoying perpetual drift if only one of these parameters needs to be updated as the other must be set to it's default value. See linked issue for more details on this behaviour.
Priority: low
Relates #9827
Output from acceptance testing: