Skip to content
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

Clean dangling DHCP Options #668

Merged
merged 5 commits into from
Mar 15, 2024

Conversation

mhajas
Copy link
Contributor

@mhajas mhajas commented Jan 3, 2024

This is a workaround for the following issue https://issues.redhat.com/browse/OCPBUGS-1838. We can watch the script output and maybe provide a reproducer for the issue if we find it.

We have around 30 DHCP options still present in our account. I left it present if anyone would like to test the script.

Signed-off-by: Michal Hajas <mhajas@redhat.com>
@kami619
Copy link
Contributor

kami619 commented Jan 4, 2024

would this become moot once we switch to AWS CDK ? @mhajas

@mhajas
Copy link
Contributor Author

mhajas commented Jan 4, 2024

Not sure what you mean @kami619. Like I should write this code using AWS CDK? Or that we won't need this when we use AWS CDK?

@kami619
Copy link
Contributor

kami619 commented Jan 4, 2024

I mean, we might not have to handle the iterative deletes once we implement delete objects with AWS CDK. But we could still use this for the time being.

@ahus1
Copy link
Contributor

ahus1 commented Jan 5, 2024

IMHO DHCP Options are dangling resources from a ROSA cluster creation, which we might not (never?) create via CDK.

So IMHO this is valid to keep as a CLI automated cleanup.

@kami619 kami619 self-requested a review March 13, 2024 13:54
Signed-off-by: Kamesh Akella <kamesh.asp@gmail.com>
Signed-off-by: Kamesh Akella <kamesh.asp@gmail.com>
@kami619 kami619 merged commit 5e3a24e into keycloak:main Mar 15, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants