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(secret): add rw_catalog.rw_secrets table #17726

Merged
merged 1 commit into from
Jul 30, 2024
Merged

Conversation

yuhao-su
Copy link
Contributor

@yuhao-su yuhao-su commented Jul 17, 2024

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

add rw_catalog.rw_secrets table

One problem is secret backend was encrypted. So no backend info in the system table. @tabVersion

Checklist

  • I have written necessary rustdoc comments
  • I have added necessary unit tests and integration tests
  • I have added test labels as necessary. See details.
  • I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features Sqlsmith: Sql feature generation #7934).
  • My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
  • All checks passed in ./risedev check (or alias, ./risedev c)
  • My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)
  • My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

  • My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note

If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

Add rw_catalog.rw_secrets catalog table.

Table schema:
id: id of secret object.
name: name of the secret
owner: owner of the secret
acl: access control of the secret.

@tabVersion
Copy link
Contributor

One problem is secret backend was encrypted. So no backend info in the system table

Let's discuss in slack channel.

Copy link
Contributor

@tabVersion tabVersion left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

rest LGTM

Comment on lines +23 to +27
#[primary_key]
id: i32,
name: String,
owner: i32,
acl: String,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

wish we could add a backend column for "meta" or "HashiCrop_Vault".

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not viable for now because it's encrypted. We figure out what we can do after we add hashicorp

@yuhao-su yuhao-su added this pull request to the merge queue Jul 30, 2024
Merged via the queue into main with commit 8417d84 Jul 30, 2024
30 of 31 checks passed
@yuhao-su yuhao-su deleted the yuhao/rw_secrets branch July 30, 2024 06:26
@yezizp2012
Copy link
Member

Please mark it as user-facing and add some release notes for it.

@yuhao-su yuhao-su added the user-facing-changes Contains changes that are visible to users label Jul 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/feature user-facing-changes Contains changes that are visible to users
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants