unable to use env variable in connection resource: Function calls not allowed

[0xADD1E]

Further to turbot/pipe-fittings#149 (and the fix turbot/pipe-fittings#150)

It would be beneficial in some cases to be able to setup steampipe connection resources as follows

connection "googledirectory" {
  plugin = "googledirectory"
  token_path = env("CLOUDSDK_ADC_MYDOMAIN")
}

but when attempting to run, this yields

steampipe query
Error: Internal Error: Failed to load config: Function calls not allowed: Functions may not be called here.
(/Users/kaja/Documents/Code/Steampipe/config/googledirectory.spc:3,16-56)

Version info: Steampipe v1.0.0 on arm64 macOS 15.1 (24B82)

[pskrbasu]

Hey @0xADD1E it seems like Steampipe connections do not support functions currently.

The issue and the fix you have tagged are related to Flowpipe and not Steampipe. Flowpipe credentials currently support functions.

Hence I'm transferring this issue to the steampipe repo and marking it as a new Feature Request. This will be a good addition and we will work on it. Thanks for bringing this to our attention. 😊

[0xADD1E]

Hey @pskrbasu - apologies for the confusion,
While the issue here is specific to Steampipe, I thought the config parser Steampipe used for connections was the same pipe-fittings/parse module that was used by Flowpipe (just connection.go instead of credential.go).
Am I misunderstanding the module structure here, or is this saying there's a better way of doing this for Steampipe?

[kaidaguerre]

Hey @0xADD1E

You are correct that Steampipe connection parsing happens in pipe-fittings. However the connection structure of Steampipe connections and Flowpipe/Powerpipe connections (PipelingConnections) is different - thus there is a different set of parsing code. This this problem is Steampipe specific.

At present the Steampipe connection parsing code does not support functions. This is more a for historical reasons rather than any technical reason and I certainly think it's reasonable to add this support. I don't foresee issues buit let me take a look into it

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.