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

feat: Disabling profiling results from "secret" and "official" datasets #482

Merged

Conversation

dlpzx
Copy link
Contributor

@dlpzx dlpzx commented May 26, 2023

Feature or Bugfix

  • Feature

Detail

  • For datasets that are classified as "Secret", data preview is disabled. In the same way, data profiling results should alse be denied.
    image

Relates

@dlpzx dlpzx changed the title check permissions in profilin feat: Disabling profiling results from "secret" datasets May 26, 2023
@dlpzx dlpzx requested a review from nikpodsh June 1, 2023 11:26
@dlpzx
Copy link
Contributor Author

dlpzx commented Jun 1, 2023

@nikpodsh I just tested the 3 scenarios: secret, official and unclassified and it works as expected:
With the following error appearing for secret and official datasets (tables):
image

@dlpzx dlpzx changed the title feat: Disabling profiling results from "secret" datasets feat: Disabling profiling results from "secret" and "official" datasets Jun 1, 2023
@dlpzx dlpzx requested a review from nikpodsh June 2, 2023 09:50
@dlpzx dlpzx merged commit 856a721 into v1m6m0 Jun 2, 2023
@dlpzx dlpzx mentioned this pull request Jul 11, 2023
@dlpzx dlpzx deleted the feature/disable-profiling-results-view-to-secret-datasets branch July 14, 2023 10:19
dlpzx added a commit that referenced this pull request Jul 19, 2023
### 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>
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