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

Registry tool: wanted - a representation for approvals #1140

Open
timburks opened this issue Apr 4, 2023 · 3 comments
Open

Registry tool: wanted - a representation for approvals #1140

timburks opened this issue Apr 4, 2023 · 3 comments

Comments

@timburks
Copy link
Contributor

timburks commented Apr 4, 2023

We would like to represent approvals in the registry to support lifecycle-related governance checks. We can represent arbitrary records with FieldSets, but I think this might be a specific enough requirement to call for a specific type. Initially I think we would just accept arbitrary claims, but we might eventually allow digital signatures or MACs to be added to validate stored approvals.

@theganyo
Copy link
Member

theganyo commented Apr 4, 2023

Do we understand well enough how our approval lifecycle should work to implement this?

@earth2marsh
Copy link
Contributor

I'm not sure we should have much opinion on what the approval lifecycle should be, as it can vary a lot by company. Seems to me that it should be able to represent whether a claim is needed or given, but ideally that happens in an external system that manages that business process, such as ServiceNow.

@timburks
Copy link
Contributor Author

timburks commented Apr 4, 2023

How about this as a starting point? "We would like to support lifecycle-related governance checks in the registry." (would we?)

@timburks timburks moved this to Todo in Apigee API Registry Apr 5, 2023
@timburks timburks moved this from Todo to Discussion in Apigee API Registry Apr 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Discussion
Development

No branches or pull requests

3 participants