-
Notifications
You must be signed in to change notification settings - Fork 11
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
Add support for detailed workflow status #204
Comments
The sub-task messages should look like below Generate Security Thumbprints Input Data post-validation completed!
Validate Security Thumbprints post-validation completed!
Generate input for Trust Certificates post-validation completed!
Trust Certificates post-validation completed!
Generate input for Import SSH Keys post-validation completed! |
Hey @pradeep17j I've been experimenting with this for a while now and my idea is slightly different than what you've proposed. |
This is certainly more aligned with common Terraform operations. 🔥 🚀 |
#227 has been merged. Integration of the task tracker will need to be added on a per resource / data source as required. Once integrated, to enable the new logging one must set |
'Marking this issue as stale due to inactivity. This helps us focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. |
I'm going to lock this issue because it has been closed for 30 days. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Code of Conduct
Description
When bringup is happening, the output from
terraform apply
command says:This does not give any insight into what is happening in the background. Also when there is a failure, we will have to login to CB or SDDC to find the point of failure.
A task API like below returns back the detailed status of sub-task in progress.
https://10.0.0.215/v1/sddcs/290051a3-1725-4edc-9df9-6e94655cec0d
The CB UI utilizes this API to display the granular detail of sub-task in progress.
The provider also should utilize this API and display the details instead of
"Still creating ....." message.
Use Case(s)
Will help user get a granular view of sub-task in progress.
Potential Configuration
A detailed display for long running tasks.
References
No response
The text was updated successfully, but these errors were encountered: