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

[BUG] Apply the same timeouts for civo_instance that are available for civo_kubernetes #298

Closed
fernando-villalba opened this issue Aug 2, 2024 · 0 comments · Fixed by #303
Labels
bug Something isn't working

Comments

@fernando-villalba
Copy link
Contributor

fernando-villalba commented Aug 2, 2024

Description

civo_kubernetes resource has the following timeouts defined:

  • create (String) sets timeout for cluster creation - default 30 minutes
  • delete (String) sets timeout for cluster deletion - default 30 minutes
  • update (String) sets timeout for cluster update - default 30 minutes

However civo_instance has only create timeouts defined

Acceptance Criteria

  • For the sake of consistency, provide the same available options for both instance and kubernetes (and perhaps consider applying it to every resource progressively
@fernando-villalba fernando-villalba added the bug Something isn't working label Aug 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant