v2 changes of platform settings#447
Merged
Merged
Conversation
ritwik-g
reviewed
Jul 4, 2024
ritwik-g
reviewed
Jul 4, 2024
ritwik-g
reviewed
Jul 4, 2024
ritwik-g
reviewed
Jul 4, 2024
ritwik-g
reviewed
Jul 4, 2024
ritwik-g
reviewed
Jul 4, 2024
ritwik-g
approved these changes
Jul 4, 2024
ritwik-g
left a comment
Contributor
There was a problem hiding this comment.
Overall looks okay. Would be better if we enrich error logs.
…pstack/unstract into feat/MultiTenancyV2-Platform-settings
Contributor
Author
Addressed All comments |
vishnuszipstack
approved these changes
Jul 5, 2024
vishnuszipstack
left a comment
Contributor
There was a problem hiding this comment.
Left a NIT comment, others looks good.
Co-authored-by: Chandrasekharan M <117059509+chandrasekharan-zipstack@users.noreply.github.com> Signed-off-by: ali <117142933+muhammad-ali-e@users.noreply.github.com>
Co-authored-by: Chandrasekharan M <117059509+chandrasekharan-zipstack@users.noreply.github.com> Signed-off-by: ali <117142933+muhammad-ali-e@users.noreply.github.com>
|
Please retry analysis of this Pull-Request directly on SonarCloud |
This was referenced Jul 8, 2024
This was referenced Jul 10, 2024
Contributor
|
|
Contributor
|
We can take care of duplication when we delete v1 eventually. Bypassing. |
pk-zipstack
pushed a commit
that referenced
this pull request
Aug 20, 2025
* v2 changes of platform settings * considered optional params * Addressed Pr comments, Removed unnecessory handling of generic exceptions * Update backend/platform_settings_v2/exceptions.py Co-authored-by: Chandrasekharan M <117059509+chandrasekharan-zipstack@users.noreply.github.com> Signed-off-by: ali <117142933+muhammad-ali-e@users.noreply.github.com> * Update backend/platform_settings_v2/exceptions.py Co-authored-by: Chandrasekharan M <117059509+chandrasekharan-zipstack@users.noreply.github.com> Signed-off-by: ali <117142933+muhammad-ali-e@users.noreply.github.com> * optimized toggle_platform_key_status function * Added TODO comment for a task --------- Signed-off-by: ali <117142933+muhammad-ali-e@users.noreply.github.com> Co-authored-by: Chandrasekharan M <117059509+chandrasekharan-zipstack@users.noreply.github.com> Co-authored-by: Hari John Kuriakose <hari@zipstack.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.


What
Why
How
platform_auth_helper.pyto update the import statements from v2.platform_auth_service.pyto import from v2 applications and updated the methods of get_organization by using user context.serializers.pyto reflect import changes.apps.py.views.pyfor consistency with the new application structure.Changed files:
Can this PR break any existing features. If yes, please list possible items. If no, please explain why. (PS: Admins do not merge the PR without this section filled)
multi_tenancy_v2.Database Migrations
Env Config
Relevant Docs
Related Issues or PRs
Dependencies Versions
Notes on Testing
Screenshots
Checklist
I have read and understood the Contribution Guidelines.