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

Feature Request: max_retries option for provider block #96

Closed
kbruner opened this issue Dec 7, 2017 · 2 comments
Closed

Feature Request: max_retries option for provider block #96

kbruner opened this issue Dec 7, 2017 · 2 comments

Comments

@kbruner
Copy link

kbruner commented Dec 7, 2017

Requesting support for a max_retries option for the kubernetes provider.

Sample use case: When creating a cluster via terraform, I also want to populate some ConfigMaps with terraform outputs. It does take a few minutes for the kubernetes API to come up, so being able to increase the retry limit so the resources can live in the same .tf files as the cluster infrastructure and succeed on the same terraform apply.

@paultyng
Copy link
Contributor

paultyng commented Aug 5, 2019

This seems like the upstream progressive apply issue: hashicorp/terraform#4149

You cannot currently chain together a provider's config with the output of a resource (including a resource creating that cluster).

@paultyng paultyng closed this as completed Aug 5, 2019
@rchernobelskiy
Copy link

Is there a way to have it retry if the api server has a momentary hiccup?

(Just as an aside, the progressive apply works fine with aws/eks)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants