-
Notifications
You must be signed in to change notification settings - Fork 82
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
feat: add share reason in share requests #498
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in general it looks good
Finished writing unit tests - ready for another review |
backend/migrations/versions/72b8a90b6ee8__share_request_purpose.py
Outdated
Show resolved
Hide resolved
I just checked the following:
For the frontend I think we could have something a bit more organised. On the right we have the request details and on the left the dataset details. I would place the request purpose on the request details or in a different box like in this screenshot: I did some testing in 9c75ac1, if you want (only if you want) you can take it as reference |
I like this frontend design screenshot better - let me add that separate box and get a new commit up |
Latest Commit:
|
|
||
|
||
def downgrade(): | ||
# ### commands auto generated by Alembic - please adjust! ### |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We are missing the back-filling when downgrading. I know, we hardly ever downgrade, but once I had a customer that needed to downgrade and it was crucial that migrations were both-sided
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just updated the PR with code for downgrading and did tests on both upgrade and downgrade again on the Aurora DB
Validated the resource permissions and columns got upgraded and downgraded as expected. @dlpzx - Think we are good here if you want to do one last final review
@@ -1031,6 +1063,7 @@ def list_user_received_share_requests( | |||
f'{{{username}}}' | |||
), | |||
models.Dataset.stewards.in_(groups), | |||
models.Dataset.SamlAdminGroupName.in_(groups), | |||
) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good catch!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
final final details
@@ -764,6 +765,7 @@ const ShareView = () => { | |||
<Typography | |||
color="textPrimary" | |||
variant="subtitle2" | |||
sx={{ wordBreak: "break-word" }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thanks for including so many small fixes in this PR. I also re-tested the migration up and down an it is 🥇
### Feature or Bugfix Release PR with the following list of features. Refer to each PR for the details ### Detail - #498 - #482 - #543 - #524 (which also solves #531) - #532 - #535 - #497 - #515 - #529 - #562 - #455 - #572 - #567 - #573 - #579 - #578 - #582 ### Breaking changes - release notes -⚠️ IMPORTANT: upgrade to a version >V1.5.0 before upgrading to V1.6 to avoid deletion of resources in custom resource deletion -⚠️ IMPORTANT: requires an update of environments and then datasets after upgrading. Either using cdk.json parameter `enable_update_dataall_stacks_in_cicd_pipeline`, waiting for overnight update stack task, or manually updating first environments and then datasets - CloudFront distribution replace for #529 - Additional EC2 permissions in CDK Synth CodeBuild stage for #543 --> this can be avoided by upgrading to v1.5.6 before upgrading to v1.6.0 - local development affected by more restrictive pivotRole trust policy ### Relates V1.6.0 release By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license. --------- Co-authored-by: Gezim Musliaj <102723839+gmuslia@users.noreply.github.com> Co-authored-by: Noah Paige <69586985+noah-paige@users.noreply.github.com> Co-authored-by: nikpodsh <124577300+nikpodsh@users.noreply.github.com> Co-authored-by: chamcca <40579012+chamcca@users.noreply.github.com> Co-authored-by: Nikita Podshivalov <nikpodsh@amazon.com> Co-authored-by: dbalintx <132444646+dbalintx@users.noreply.github.com> Co-authored-by: mourya-33 <134511711+mourya-33@users.noreply.github.com>
Feature or Bugfix
Detail
Relates
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.