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 limit_workspaces to user model #529

Merged
merged 1 commit into from
Jun 4, 2024
Merged

add limit_workspaces to user model #529

merged 1 commit into from
Jun 4, 2024

Conversation

nat-fastly
Copy link
Contributor

@nat-fastly nat-fastly commented Jun 4, 2024

The Fastly UI needs to read the limit_workspaces attribute from the GET /user/:user_id response in order to determine whether to display the list of workspaces on the user management screen for each user

Copy link
Collaborator

@Integralist Integralist left a comment

Choose a reason for hiding this comment

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

One minor comment, otherwise LGTM.

@@ -13,6 +13,7 @@ type User struct {
DeletedAt *time.Time `mapstructure:"deleted_at"`
EmailHash *string `mapstructure:"email_hash"`
LimitServices *bool `mapstructure:"limit_services"`
LimitWorkspaces *bool `mapstructure:"limit_workspaces"`
Copy link
Collaborator

Choose a reason for hiding this comment

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

I was checking the customer API https://www.fastly.com/documentation/reference/api/account/customer/ and I don't see the limit_workspaces field documented. It's not a blocker for this PR but it's usually a good idea to make sure the docs are updated to reflect the latest interface.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@Integralist thank you for reviewing this! We're planning to update the API docs after we release this change

@nat-fastly nat-fastly merged commit 217726f into main Jun 4, 2024
4 checks passed
@nat-fastly nat-fastly deleted the pxeng-6531 branch June 4, 2024 15:08
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