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

Provider does not understand user's status 'Pending user action' #100

Closed
mszewczyk-ipwt opened this issue May 26, 2021 · 1 comment
Closed
Assignees
Labels
awaiting-feedback Blocked on input from the author kind/bug Some behavior is incorrect or out of spec resolution/no-repro This issue wasn't able to be reproduced

Comments

@mszewczyk-ipwt
Copy link

provider reports resource error during refresh:

error: okta:user/user:User resource 'user' has a problem: expected [{{} status}] to be one of ACTIVE,STAGED,DEPROVISIONED,SUSPENDED, got PROVISIONED. Examine values at 'User.Status'.

Expected behavior

Status of the user should be refreshed with no errors

Current behavior

error reported like above

Steps to reproduce

  1. Create a user using User class in okta.user provider with no password - okta sends emails when no password is provided.
  2. After first update user's status on page is 'Pending user action'.
  3. Refresh the stack with that user's status.

Context (Environment)

Using Python:

Python 3.9.2

Okta provider:

NAME        KIND      VERSION  SIZE    INSTALLED  LAST USED
okta        resource  3.0.0    42 MB   n/a        1 hour ago

Pulumi:

► pulumi version
v3.2.1

Affected feature

I am using pulumi to automte the process of creating users and in every procedure I refresh the status of the users. When not supported status appears then no action is taken and the process results in exit code 1.

@mszewczyk-ipwt mszewczyk-ipwt added the kind/bug Some behavior is incorrect or out of spec label May 26, 2021
@lukehoban lukehoban added kind/bug Some behavior is incorrect or out of spec and removed kind/bug Some behavior is incorrect or out of spec labels May 28, 2021
@mjeffryes
Copy link
Member

Unfortunately, it looks like this issue hasn't seen any updates in a while. If you're still encountering this problem, could you leave a quick comment to let us know so we can prioritize it?

@mjeffryes mjeffryes added the awaiting-feedback Blocked on input from the author label Sep 26, 2024
@mjeffryes mjeffryes added the resolution/no-repro This issue wasn't able to be reproduced label Oct 25, 2024
@mjeffryes mjeffryes self-assigned this Nov 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting-feedback Blocked on input from the author 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

3 participants