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

[Feature Request] Ability to set custom attributes for the user resource #67

Open
emtunc opened this issue Jul 16, 2021 · 5 comments
Open

Comments

@emtunc
Copy link

emtunc commented Jul 16, 2021

We would love to be able to manage user resources via TF but the lack of support for custom attributes is a real blocker for us.

Would it be possible to add support for defining custom attributes to the user resource?

@duncanboa
Copy link

I second this - we use custom attributes in tons of our mappings. If we can't set them via terraform we're forced to manage the users via the admin console (which we prefer not to do because it means granting more people admin permissions)

@hendrikhalkow
Copy link

It's already there – see custom_attributes.

@duncanboa
Copy link

I think this is missing from the documentation then as there is no reference to it here

@duncanboa
Copy link

Works if you do this:

resource "onelogin_users" "test_account" {
  username = "username"
  email    = "user@domain.com"
  company  = "Made Up"
  custom_attributes = {
    division     = "Something"
    mission_team = uuid()
  }
}

@cdg-benny-bennybustam
Copy link

cdg-benny-bennybustam commented Jul 19, 2023

Hi, same here, I have this issue using custom_attributes on v0.4.9, it giving me this error messages. Any idea, is the custom_attributes suppported on v0.4.9?

Error: Unsupported argument
│ 
│   on auto.tf line 16, in resource "onelogin_users_v1" "this":
│   16:   custom_attributes = {
│ 
│ An argument named "custom_attributes" is not expected here.

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

No branches or pull requests

4 participants