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

auth0.Connection constructor strategy_version appears to be ignored #154

Open
ryanrasti opened this issue Aug 2, 2022 · 2 comments
Open
Labels
kind/bug Some behavior is incorrect or out of spec

Comments

@ryanrasti
Copy link

What happened?

The constructor argument of auth0.Connection strategy_version and corresponding Output appear to be ignored.

It does, however, work when using the options constructor arg/output.

Steps to reproduce

Create a connection like so:

    microsoft = auth0.Connection(
        'microsoft',
        enabled_clients=[client.id],
        strategy='windowslive',
        strategy_version=2
    )

does NOT create an Auth0 connection with strategy version 2 (it uses default strategy version 1). Similiarily, looking up an existing connection

auth0.Connection.get('msft', id=...)

does not return a strategy_version in its Outputs.

Expected Behavior

Auth0 connection created with strategy_version set to 2

Actual Behavior

Auth0 connection created with (default?) strategy_version set to 1

Versions used

CLI
Version 3.35.2
Go Version go1.17.11
Go Compiler gc

Host
OS debian
Version bookworm/sid
Arch x86_64

Auth0 version: pulumi_auth0-2.11.0

Additional context

To actually set strategy version, one must use options. (i.e., the following WORKS):

    microsoft = auth0.Connection(
        'microsoft2',
        enabled_clients=[client.id],
        strategy='windowslive',
        options=auth0.ConnectionOptionsArgs(
            strategy_version=2
        ),
    )

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).

@ryanrasti ryanrasti added kind/bug Some behavior is incorrect or out of spec needs-triage Needs attention from the triage team labels Aug 2, 2022
@stack72
Copy link
Contributor

stack72 commented Aug 3, 2022

Hi @ryanrasti

I apologise for the issue here - this is due to an old version of the schema in terraform that is migrating the state of the property. This should be omitted - I will get a new version of the provider upgraded and taken care of

Paul

@stack72 stack72 self-assigned this Aug 3, 2022
@stack72 stack72 removed the needs-triage Needs attention from the triage team label Aug 3, 2022
@stack72 stack72 removed their assignment Sep 8, 2022
@guineveresaenger
Copy link
Contributor

Hi @ryanrasti - can you try the latest version of this provider and see if the issue persists? Thank you for your patience. 🙇‍♀️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Some behavior is incorrect or out of spec
Projects
None yet
Development

No branches or pull requests

3 participants