Skip to content
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

signalfx_org_token secret attribute does not work #310

Closed
Yonas-Dresen opened this issue Jul 29, 2021 · 2 comments · Fixed by #392
Closed

signalfx_org_token secret attribute does not work #310

Yonas-Dresen opened this issue Jul 29, 2021 · 2 comments · Fixed by #392

Comments

@Yonas-Dresen
Copy link

Hello SignalFx team,

According to the documentation of the SignalFx terraform provider. In the signalfx_org_token resource you can request the secret attribute after creation.
https://registry.terraform.io/providers/splunk-terraform/signalfx/latest/docs/resources/org_token#secret

This attribute is returning 'null' at all times. When using TF_LOG=DEBUG you can clearly see the secret that the api returned, but the SignalFx provider does not store or fails to store the secret in the Terraform state file.

@mjhuber
Copy link

mjhuber commented Aug 16, 2022

seeing this issue as well in version 6.14.0. Example:

resource "signalfx_org_token" "token" {
  name        = "stage-test"
  description = "stage-test"
}

and then looking at the state, secret is null but the token was created in signalfx.

    {
      "mode": "managed",
      "type": "signalfx_org_token",
      "name": "token",
      "provider": "provider[\"registry.terraform.io/splunk-terraform/signalfx\"]",
      "instances": [
        {
          "schema_version": 0,
          "attributes": {
            "auth_scopes": [
              "API",
              "INGEST"
            ],
            "description": "stage-test",
            "disabled": false,
            "dpm_limits": [],
            "host_or_usage_limits": [],
            "id": "stage-test",
            "name": "stage-test",
            "notifications": null,
            "secret": null
          },
          "sensitive_attributes": [],
          "private": "<redacted>",
          "dependencies": [
            "data.vault_generic_secret.signalfx_creds"
          ]
        }
      ]
    },

@mjhuber
Copy link

mjhuber commented Sep 15, 2022

update for anyone watching, this is now fixed in provider version 6.17.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants