Add debug logging to cloudstack provider

[glenjamin]

I'm happy to provide a PR for this, I wanted to check on the general policy for debug logging first.

At the moment it can be a little tricky to debug cloudstack failures, as there's nothing in the logs to show which API was called, and with what parameters.

I can see two options here to improve this story

1. Add debug logging capabilities into go-cloudstack, based on an environment variable
2. Add debug logging next to every go-cloudstack api call in the terraform profider, which would respect TF_LOG

The latter would probably be simpler, as it it doesn't require a new way of enabling debug logging. Is there a general policy for what should or shouldn't be included in the TF_LOG output?

[svanharmelen]

@phinze I don't think there is a policy for this right? As long as common sense is used, it should be fine IMHO...

[phinze]

Agreed! @glenjamin you can just go ahead with (2) and add debug logging to the provider.

[svanharmelen]

@glenjamin are you ok with me closing this one? Think your question is answered and your good to go write some logging right?

Also please keep an eye on PR #3380 as it seems that one will be merged shortly and it improves/extends the logging capabilities if TF.

[glenjamin]

It's vaguely on my todo, might be better off keeping it open in case someone else wants to pick it up?

[svanharmelen]

Well in that case I'll go ahead and close it off... 😉 With well over 500 open issues I don't think it adds much value to leave this one open as well. Especially since the question in the issue is answered and can be found back by others when searching through the issues.

Thanks!

[ghost]

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.