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

Typescript Client Metadata type not consistent with terraform #58

Closed
gjolund opened this issue Jan 31, 2021 · 1 comment
Closed

Typescript Client Metadata type not consistent with terraform #58

gjolund opened this issue Jan 31, 2021 · 1 comment
Labels
area/providers kind/bug Some behavior is incorrect or out of spec resolution/no-repro This issue wasn't able to be reproduced

Comments

@gjolund
Copy link

gjolund commented Jan 31, 2021

The type defined for for the Client.clientMetadata custom resource property is incorrect.

    /**
     * Map(String)
     */
    readonly clientMetadata: pulumi.Output<{
        [key: string]: any;
    } | undefined>;

When attempting to set client metadata to something like

{
  clientMetada: {
    hasura: hasura.jwtClaimsNamespace,
  }
}

You get the following error

error: auth0:index/client:Client resource 'auth0-account-linking-client' has a problem: client_metadata (claimsNamespaces): '' expected type 'string', got unconvertible type 'map[string]interface {}', value: 'map[hasura:https://hasura.io/jwt/claims]'

It seems as though the terraform provider is expecting a string map whereas the pulumi provider is an any map.

@infin8x infin8x added kind/bug Some behavior is incorrect or out of spec and removed bug labels Jul 10, 2021
@mikhailshilkov mikhailshilkov added the resolution/no-repro This issue wasn't able to be reproduced label Nov 28, 2023
@mikhailshilkov
Copy link
Member

I failed to reproduce this issue with a modern provider version. I set

    clientMetadata: {
        foo: "zoo",
    },

as in our API docs and did not receive a validation error.

I'll go ahead and close the issue. If anyone still experiences this problem, please report back.

@mikhailshilkov mikhailshilkov closed this as not planned Won't fix, can't repro, duplicate, stale Nov 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/providers kind/bug Some behavior is incorrect or out of spec resolution/no-repro This issue wasn't able to be reproduced
Projects
None yet
Development

No branches or pull requests

4 participants