Skip to content

Conversation

@strantalis
Copy link
Member

Remove all nanoTDF references from public documentation and code samples as the feature is being made proprietary.

Changes

  • Removed KAS NanoTDF rewrap section and diagram from Key Access documentation
  • Deleted NanoTDF code samples (Java collection examples, TDF encryption example)
  • Removed NanoTDF feature matrix entries and constraints in base key documentation
  • Updated OpenAPI spec descriptions to remove nanoTDF-specific language
  • Updated build configuration to stop generating nanoTDF specification pages

Note

OpenAPI specs in /specs are vendored from upstream. Local modifications will be overwritten when running npm run update-vendored-yaml. The upstream opentdf/platform repository should be updated separately.

@strantalis strantalis requested a review from a team as a code owner January 21, 2026 14:10
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @strantalis, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on a significant cleanup effort by removing all public-facing documentation and code samples pertaining to the nanoTDF feature. This change reflects the feature's new proprietary status, ensuring that the public documentation accurately represents the available open-source offerings. The updates span across various documentation files, code examples, OpenAPI specifications, and build configurations to eliminate any mention or generation of nanoTDF-related content.

Highlights

  • NanoTDF Documentation Removal: All public documentation and code samples related to nanoTDF have been removed, aligning with the feature's transition to proprietary status.
  • OpenAPI Specification Updates: Descriptions within various OpenAPI specifications have been generalized to remove explicit nanoTDF references, replacing them with broader terms like "EC-based wrapping" or "formats that embed it."
  • Build Configuration Streamlining: The build process has been updated to cease generating nanoTDF-specific documentation pages, ensuring a cleaner public documentation site.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request effectively removes most references to nanoTDF from the documentation, code samples, and build configurations, aligning with the goal of making the feature proprietary. The changes are generally well-executed. However, I've identified a critical issue in one of the Java code samples where a typo was introduced. Additionally, this particular code sample file, being a nanoTDF example, seems to have been overlooked for deletion as per the PR's objective. Please see the specific comment for details.

Copy link
Member

@pflynn-virtru pflynn-virtru left a comment

Choose a reason for hiding this comment

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

statis/img has newly added nano images

@strantalis strantalis force-pushed the strantalis/remove-nanotdf-docs branch from 3aa9f93 to 32a3146 Compare January 21, 2026 14:45
Remove all nanoTDF documentation, code samples, and API spec descriptions
as the feature is being made proprietary. This includes the KAS NanoTDF
rewrap section, code examples, SDK feature matrix entries, and OpenAPI
spec mentions.
@strantalis strantalis force-pushed the strantalis/remove-nanotdf-docs branch from 32a3146 to 05a88b8 Compare January 21, 2026 16:35
@strantalis strantalis merged commit b39db23 into main Jan 21, 2026
4 checks passed
@strantalis strantalis deleted the strantalis/remove-nanotdf-docs branch January 21, 2026 17:01
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

Successfully merging this pull request may close these issues.

3 participants