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

Improve terraform cloudflare broker UX in face of timeout #22

Open
gberche-orange opened this issue Jan 29, 2018 · 0 comments
Open

Improve terraform cloudflare broker UX in face of timeout #22

gberche-orange opened this issue Jan 29, 2018 · 0 comments

Comments

@gberche-orange
Copy link
Member

gberche-orange commented Jan 29, 2018

Currently, when a timeout is encountered the cloudflare broker displays a message such "failed, timeout encounted 903s, max is 900". The service instance request (create or delete) remains in the failed state, even if in some cases the provisionning proceeds and eventually successfully completes.

The current workaround is for users to request to delete the failed service instance, wait for successful completion, and create a new service instance. If delete request also fails, human support should be asked for.

Suggested improvements:

  1. The returned message should hint users about this potential workaround
  2. COAB could support a debug-mode=false into which any failure automatically results in automatic unprovisionning (ie COAB desired state removed the TF module). When debug-mode=true is enabled, the failed provisionning is left as-is for operators to troubleshoot and possibly repair (such as in the case of Regression: IAAS_SPEC_PATH is missing in Concourse pipelines  cf-ops-automation#151
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

No branches or pull requests

1 participant