Every action on the provider results in the api calls being output to the console.

[zbuchheit]

What happened?

While using the provider, all resources I was creating or functions I was using resulted in the corresponding api call being logged to the output.

Example

import * as pulumi from "@pulumi/pulumi";
import * as ise from "@pulumi/ise";


    const username = process.env["ISE_USERNAME"] || "";
    const password = process.env["ISE_PASSWORD"] || "";
    if (username === "" || password === "") {
        throw new Error("Missing ISE username and/or password");
    }

    const url = process.env["ISE_URL"] || "";
    if (url === "") {
        throw new Error("Missing ISE URL");
    }

    const provider = new ise.Provider("ise", {
        username: username,
        password: password,
        url: url,
        retries: 0
    });

    const pulumiEmployeeGroup = new ise.identitymanagement.UserIdentityGroup("pulumi-employee-group", {
        name: "PulumiEmployeeGroup",
        description: "My pulumi employee identity group",
    });

Updating (dev):
     Type                                         Name                   Status              Info
 +   pulumi:pulumi:Stack                          zbuchheit-ise-dev      created (2s)        3 messages
 +   ├─ pulumi:providers:ise                      ise                    created (0.06s)
 +   └─ ise:identitymanagement:UserIdentityGroup  pulumi-employee-group  created (0.44s)
Diagnostics:
  pulumi:pulumi:Stack (zbuchheit-ise-dev):
    2024/05/10 01:32:35 [DEBUG] HTTP Request: POST, https://{REDACTED}/ers/config/identitygroup, {{"IdentityGroup":{"name":"PulumiEmployeeGroup","description":"My pulumi employee identity group"}}}
    2024/05/10 01:32:36 [DEBUG] HTTP Response:
    2024/05/10 01:32:36 [DEBUG] Exit from Do method

Output of pulumi about

CLI
Version      3.115.2
Go Version   go1.22.2
Go Compiler  gc

Plugins
KIND      NAME    VERSION
resource  ise     0.1.1
language  nodejs  unknown

Host
OS       Microsoft Windows Server 2022 Datacenter
Version  10.0.20348 Build 20348
Arch     x86_64

This project is written in nodejs: executable='C:\Program Files\nodejs\node.exe' version='v20.13.1'

Backend
Name           EC2AMAZ-V236MOS
URL            file://~
User           EC2AMAZ-V236MOS\Administrator
Organizations
Token type     personal

Additional context

No response

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

[VenelinMartinov]

Thanks for reporting and for the detailed repro!

Unfortunately, we'd need to sort out access credentials for the provider before we can address issues here.

Opened #16

[zbuchheit]

adding some additional details to this as i have created my own instance of ISE in AWS.

In my testing, the provider is behaving as if the TF_LOG level is set to DEBUG automatically. When I test the equivalent in TF, I don't get the same behavior so this does appear to be a bug in the bridged provider.

[VenelinMartinov]

Note similar issues in Meraki and pulumi/pulumi-databricks#474.
Potentially related too: pulumi/pulumi-gitlab#514

[zbuchheit]

When digging into it, it looks like this is likely coming from the go library used. That being said, I am curious why this behaves differently in the upstream provider.

source: https://github.com/netascode/go-ise/blob/b9cb4ca5f659fcad3ca9b0d4526abcfa5766e390/client.go#L142

[iwahbe]

When digging into it, it looks like this is likely coming from the go library used. That being said, I am curious why this behaves differently in the upstream provider.

source: https://github.com/netascode/go-ise/blob/b9cb4ca5f659fcad3ca9b0d4526abcfa5766e390/client.go#L142

Terraform doesn't display provider stdout to the user by default, but we do. pulumi/pulumi-terraform-bridge#2489 tracks that discrepancy.

[zbuchheit]

I have tested pulumi/pulumi-terraform-bridge#2686 with the provider and can confirm it does fix the issue

[iwahbe]

As tested by @zbuchheit, this has been fixed by #154. The fix will be visible to users on the next release of this provider.