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

add send_invite field to opslevel_user resource #495

Merged
merged 3 commits into from
Sep 30, 2024

Conversation

davidbloss
Copy link
Contributor

Resolves #463

Problem

Solution

Checklist

  • I have run this code, and it appears to resolve the stated issue.
  • This PR does not reduce total test coverage
  • This PR has no user interface changes or has already received approval from product management to change the interface.
  • Make a changie entry that explains the customer facing outcome of this change

@@ -88,6 +90,12 @@ func (r *UserResource) Schema(ctx context.Context, req resource.SchemaRequest, r
stringvalidator.OneOf(opslevel.AllUserRole...),
},
},
"send_invite": schema.BoolAttribute{
Description: "Send an invite email even if notifications are disabled for the account.",
Default: booldefault.StaticBool(true),
Copy link
Collaborator

@rocktavious rocktavious Sep 30, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same question as before - should this be off by default? If you are doing a mass invite of users via Terraform you likely don't want to send invites? 🤔

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The other option is to not make it optional so the end user has pick

@davidbloss davidbloss merged commit 16e016d into main Sep 30, 2024
6 checks passed
@davidbloss davidbloss deleted the db/support-skip-send-user-invite branch September 30, 2024 20:11
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 this pull request may close these issues.

2 participants