Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Handle Error on clean up share and not get stuck in IN_PROGRESS status (
#1099) ### Feature or Bugfix <!-- please choose --> - Bugfix ### Detail - Scenario - Folder share item exists in an existing share object in DA<=v2.2 - DA upgrade to v2.3 - Before updating environment/pivot role - user removes folder item from existing share object - Issue - Share tries to create the managed policies in `def clean_up_share()` and remove the inline policies - Function fails since pivotRole does not have proper IAM permissions - Exception raised and share gets stuck in a REVOKE_IN_PROGRESS state + Dataset Lock Table never releases Lock for next share to process - Resolution - Wrap `def clean_up_share()` method for revoke folder item in a try/except block - ++ Remove some unused additional code ### Security Please answer the questions below briefly where applicable, or write `N/A`. Based on [OWASP 10](https://owasp.org/Top10/en/). - Does this PR introduce or modify any input fields or queries - this includes fetching data from storage outside the application (e.g. a database, an S3 bucket)? - Is the input sanitized? - What precautions are you taking before deserializing the data you consume? - Is injection prevented by parametrizing queries? - Have you ensured no `eval` or similar functions are used? - Does this PR introduce any functionality or component that requires authorization? - How have you ensured it respects the existing AuthN/AuthZ mechanisms? - Are you logging failed auth attempts? - Are you using or adding any cryptographic features? - Do you use a standard proven implementations? - Are the used keys controlled by the customer? Where are they stored? - Are you introducing any new policies/roles/users? - Have you used the least-privilege principle? How? By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
- Loading branch information