-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
(redshift-alpha): reboot Clusters for Parameter updates #22009
Comments
Thanks for the request @dontirun, this is a great feature request that I think we should have! We accept contributions - Check out our contributing guide if you're interested - there's a low chance the team will be able to address this soon but we'd be happy to review a PR 🙂 |
Having some trouble in the PR for the integration snapshots. The codebuild build is failing due to mismatched asset hashes on the new snapshot, but both locally and on a fresh gitpod it's verifying properly ❯ yarn integ-runner
Verifying integration test snapshots...
UNCHANGED integ.cluster-loggingbucket 0.931s
UNCHANGED integ.cluster-elasticip 0.935s
UNCHANGED integ.cluster-reboot 0.998s
UNCHANGED integ.database 10.763s
Snapshot Results:
Tests: 4 passed, 4 total
✨ Done in 11.31s.
|
…#22063) Closes #22009 Currently waiting on #22055 and #22059 for the assertions in the integration test to successfully run ---- ### All Submissions: * [X] Have you followed the guidelines in our [Contributing guide?](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) ### Adding new Unconventional Dependencies: * [ ] This PR adds new unconventional dependencies following the process described [here](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md/#adding-new-unconventional-dependencies) ### New Features * [X] Have you added the new feature to an [integration test](https://github.com/aws/aws-cdk/blob/main/INTEGRATION_TESTS.md)? * [X] Did you use `yarn integ` to deploy the infrastructure and generate the snapshot (i.e. `yarn integ` without `--dry-run`)? *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
Describe the feature
Add an optional
rebootForParameterChanges
property to RedshiftCluster
s that reboots the cluster when there are changes to the Parameter groupUse Case
In most cases existing Clusters must be rebooted to apply parameter changes. It would be nice to automatically reboot the Cluster instead of having to manually do it through the CLI or console
Proposed Solution
rebootForParameterChanges
propertyOn Create
andOn Update
actionsin-sync
do nothingapplying
wait and recheckpending-reboot
reboot the clusterOther Information
No response
Acknowledgements
CDK version used
N/A
Environment details (OS name and version, etc.)
N/A
The text was updated successfully, but these errors were encountered: