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

Configurable additional requirement as soft failure #283

Open
singhvikash11 opened this issue Sep 19, 2022 · 0 comments
Open

Configurable additional requirement as soft failure #283

singhvikash11 opened this issue Sep 19, 2022 · 0 comments

Comments

@singhvikash11
Copy link
Member

Summary
Guardian allows creating additional appeals as a requirement while approving the main appeal request. However, it's tightly coupled with the status of the additional appeal and the main appeal failed if the additional appeal failed.

Proposed solution
Add some sort of config in policy to make these additional appeal requirements optional and a user can proceed with the main appeal even if an additional appeal is pending or fail.

Additional context
Currently, we provide a data-retrieval appeal on a data-access project as an additional appeal permanently. Now if we want to expose another workflow on data-retrieval appeal on a data-access project for a custom duration then the additional appeal will be failed due to renew-extension and hence it'll block the main appeal too.

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

No branches or pull requests

1 participant