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

Add actions for reading metadata #73

Open
mike-marcacci opened this issue Jan 1, 2020 · 1 comment
Open

Add actions for reading metadata #73

mike-marcacci opened this issue Jan 1, 2020 · 1 comment

Comments

@mike-marcacci
Copy link
Member

We should add an action segment to all entities to "read metadata." Metadata would include viewing records (or at least version history), invocation logs, and potentially access logs in the future.

This might be introduced alongside #71 to support the feature in #72.

@mike-marcacci
Copy link
Member Author

I propose changing the action segment from v2:

(basic).(details).(scopes).(secrets).(users)

to this in v3:

(basic).(metadata).(scopes).(secrets).(users)

Currently, details is conceptually identical to secrets but when applied to authorities and credentials. These two names could thus be consolidated into the more appropriately named secrets.

The new metadata segment (taking the second position from details, per the alphabetical convention used here) would only have provisions for an r as there is currently no mechanism for writing metadata.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant