chore(sources/dataplex)!: Renaming changes across all the files related to Dataplex Toolbox#2958
chore(sources/dataplex)!: Renaming changes across all the files related to Dataplex Toolbox#2958anikasharma03 wants to merge 4 commits intogoogleapis:mainfrom
Conversation
There was a problem hiding this comment.
Code Review
This pull request renames "Dataplex" to "Knowledge Catalog" across the entire repository, including CI configurations, documentation, internal Go packages, and integration tests. The feedback provided focuses on maintaining consistent naming conventions in the documentation and fixing a minor typo in the description of the search aspect types tool.
docs/en/integrations/knowledge-catalog/tools/knowledge-catalog-search-entries.md
Outdated
Show resolved
Hide resolved
docs/en/integrations/knowledge-catalog/tools/knowledge-catalog-search-aspect-types.md
Outdated
Show resolved
Hide resolved
Yuan325
left a comment
There was a problem hiding this comment.
Might be good to update the project env var as well so users are not confused (having to use type as "knowledge-catalog" but env var with the "dataplex" name). Please update it across the docs~
we're missing updates on these files:
- .github/CODEOWNERS - folder name (we can keep the mdb group as is for now)
- .github/blunderbuss.yml - update the label name (can keep the group as is)
- .github/labels.yaml
Will dataplex be updating the official cloud docs page link? e.g. https://cloud.google.com/dataplex? If yes, we might want to update that as well. seems like some of bigquery doc that points towards that too.
Thank you!
docs/en/integrations/knowledge-catalog/prebuilt-configs/knowledge-catalog.md
Show resolved
Hide resolved
docs/en/integrations/knowledge-catalog/prebuilt-configs/knowledge-catalog.md
Outdated
Show resolved
Hide resolved
9b32fcf to
c93e28d
Compare
|
/gcbrun |
There was a problem hiding this comment.
Hi @anikasharma03 can we implement this for cases where user uses "dataplex"? With this, we shouldn't have to worrry about breaking change.
We will also need to update the following to change entryName to "knowledge-catalog" if "dataplex" is detected (this will handle all the migration when user uses our migrate subcommand):
mcp-toolbox/cmd/internal/config.go
Line 212 in c924701
We can keep all the docs updated to knowledge-catalog, no need to update those, thank you!
There was a problem hiding this comment.
can we do another copy of this file and keep the types with the "dataplex" name?
…entation, file names, directories, configurations etc to reflect the new name of the dataplex toolbox.
5749fb5 to
bd41aaa
Compare
|
/gcbrun |
| if r.Project == "" { | ||
| r.Project = os.Getenv("DATAPLEX_PROJECT") | ||
| } | ||
|
|
There was a problem hiding this comment.
Would prefer not to do this. We try not to grab environment variable from the server code post-unmarshalling. This might be flaky if the server is deployed in a separate environment as well.
| if r.Project == "" { | |
| r.Project = os.Getenv("DATAPLEX_PROJECT") | |
| } |
| // See the License for the specific language governing permissions and | ||
| // limitations under the License. | ||
|
|
||
| package knowledgecatalog_test |
There was a problem hiding this comment.
| package knowledgecatalog_test | |
| package knowledgecatalog |
| KnowledgeCatalogSearchEntriesToolType = "dataplex-search-entries" | ||
| KnowledgeCatalogLookupEntryToolType = "dataplex-lookup-entry" | ||
| KnowledgeCatalogSearchAspectTypesToolType = "dataplex-search-aspect-types" | ||
| KnowledgeCatalogProject = getProject() |
There was a problem hiding this comment.
| KnowledgeCatalogProject = getProject() | |
| KnowledgeCatalogProject = os.Getenv("DATAPLEX_PROJECT") |
| ) | ||
|
|
||
| func getProject() string { | ||
| p := os.Getenv("KNOWLEDGE_CATALOG_PROJECT") | ||
| if p == "" { | ||
| p = os.Getenv("DATAPLEX_PROJECT") | ||
| } | ||
| return p | ||
| } |
There was a problem hiding this comment.
| ) | |
| func getProject() string { | |
| p := os.Getenv("KNOWLEDGE_CATALOG_PROJECT") | |
| if p == "" { | |
| p = os.Getenv("DATAPLEX_PROJECT") | |
| } | |
| return p | |
| } | |
| ) |
There was a problem hiding this comment.
can we just keep this file as the exact same as what we have now in dataplex_integration_test.go? I don't think we will need to update anything~
| if len(dataplex_config) <= 0 { | ||
| t.Fatalf("unexpected error: could not fetch dataplex prebuilt tools yaml") |
| expectedKeys := expectedToolSources | ||
| var expectedKeys []string | ||
| for _, k := range expectedToolSources { | ||
| if k != "dataplex" { | ||
| expectedKeys = append(expectedKeys, k) | ||
| } | ||
| } |
There was a problem hiding this comment.
Let's keep as is and don't modify this~
| cloudsqlmysql_admin_config, _ := prebuiltconfigs.Get("cloud-sql-mysql-admin") | ||
| cloudsqlmssql_config, _ := prebuiltconfigs.Get("cloud-sql-mssql") | ||
| cloudsqlmssql_admin_config, _ := prebuiltconfigs.Get("cloud-sql-mssql-admin") | ||
| dataplex_config, _ := prebuiltconfigs.Get("dataplex") |
There was a problem hiding this comment.
let's keep this to make sure we implement the backwards compatibility.
| t.Setenv("API_KEY", "your_api_key") | ||
|
|
||
| t.Setenv("BIGQUERY_PROJECT", "your_gcp_project_id") | ||
| t.Setenv("DATAPLEX_PROJECT", "your_gcp_project_id") |
| name: "dataplex prebuilt tools", | ||
| in: dataplex_config, |
There was a problem hiding this comment.
let's keep this~ and add a new test case for knowledge catalog.
|
Closing since we are no longer renaming the src code. |
Description
Perform a full rename across files and directories related to the Dataplex Toolbox . This wide-scale refactoring is needed to ensure consistency across the entire codebase and documentation.
Key Changes
File and Directory Renaming:
Moved and renamed all directories and files associated with the dataplex implementation to follow the new naming convention (e.g., in internal/tools/, internal/sources/, and tests/).
Documentation Updates:
Updated references in README.md, integration guides, and other documentation files to reflect the new component naming.
Code Refactoring:
Updated internal references, variable names, and configuration keys to match the new naming standard while maintaining functional compatibility.
Test Updates:
Renamed test files and updated test cases to ensure they correctly validate the renamed components.
PR Checklist
CONTRIBUTING.md
bug/issue
before writing your code! That way we can discuss the change, evaluate
designs, and agree on the general idea
!if this involve a breaking change🛠️ Fixes #2956