Closed doctornkz closed 4 months ago
A great question! At present, a lot of this is encoded into the Terraform provider. We could definitely move it here. I'll say that this is lower priority to me than some other Terraform provider features, though.
One more question: cli exporter? As of last week the provider now supports terraform import
which means you can pretty easily import and get the configuration for any asset. Does that suit your needs? There is also signalfx-to-terraform which is rather rough…
terraform import
but looks it can't import signalFX json as is.
Jinja-template programming hard way for our users. Also I prefer to use native upstream libraries from signalfx/terraform
instead json/string/dict manipulation with python. But I agree - one more bicycle reinvention
from my side )Found the really funny stuff: int: https://github.com/signalfx/signalfx-go/blob/master/chart/model_event_publish_label_options.go#L6 int32 https://github.com/signalfx/signalfx-go/blob/master/chart/model_publish_label_options.go#L18 but semantically it should be the same )
@cory-signalfx , jfyi: https://github.com/doctornkz/signalfx2terraform , we are using this tool to export data from API.
So many years already ) But I am fine with that.
Yes, roughly 5 years made it seem to me like it was time to close the issue. We can open a Splunk idea (ideas.splunk.com) to follow up if you'd like.
No, thank you @atoulme, I am not with signalfx/splunk tech stack anymore. But your action reminded me of all @cory-signalfx efforts. Wish you, folks, all the best.
Hi contributors, I hope that issue can't break your Monday motivation! Right now I am working hard on my
signalFX->terraform configuration
cli-exporter. And I am stucked with two problems: