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

Fix free users can't create datasets due to default state was private #16223

Conversation

Josmorsot
Copy link
Contributor

@Josmorsot Josmorsot commented Mar 16, 2021

https://app.clubhouse.io/cartoteam/story/138033/free-academic-users-invalid-import-when-using-the-ui

Summary:
Free users were trying to import datasets, by default we had privacy as PRIVATE but they can't import private datasets

@shortcut-integration
Copy link

This pull request has been linked to Clubhouse Story #138033: [Free-Academic users] Invalid import when using the UI.

NEWS.md Outdated Show resolved Hide resolved
@@ -11,3 +11,4 @@ export const accountsWithApiKeysLimitsToZero = free2020;

export const accountsWithDataCatalogLimits = [...free2020, ...free, ...student];
export const accountsWithOauthAppsLimits = [...free2020, ...free, ...student];
export const accountsWithDefaultPublic = [...free2020, ...free, ...student];
Copy link
Contributor

Choose a reason for hiding this comment

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

Looks like a better approach, 👍🏻

@VictorVelarde VictorVelarde changed the title BUGFIX: was trying to create private dataset for accounts were not available Fix free users can't create datasets due to default state was private Mar 17, 2021
@VictorVelarde
Copy link
Contributor

LGTM, are you deploying a staging for acceptance?

Copy link
Contributor

@jgoizueta jgoizueta left a comment

Choose a reason for hiding this comment

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

LGTM

Sorry for the delay, it took me too long to verify the behaviour of the import backend when the privacy parameter is not present.

If the privacy parameter is blank/missing the backend will do the proper thing: default to private for users with private tables and public otherwise. So if you prefer to always omit the parameter, that would be fine too.

@Josmorsot Josmorsot merged commit ed7a773 into master Mar 31, 2021
@Josmorsot Josmorsot deleted the feature/ch138033/free-academic-users-invalid-import-when-using branch March 31, 2021 17:55
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.

4 participants