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

[FEATURE] Create a ucx catalog via a cli-command #2571

Closed
Tracked by #2074
JCZuurmond opened this issue Sep 11, 2024 · 2 comments · Fixed by #2694
Closed
Tracked by #2074

[FEATURE] Create a ucx catalog via a cli-command #2571

JCZuurmond opened this issue Sep 11, 2024 · 2 comments · Fixed by #2694
Assignees
Labels
feat/migration-progress Issues related to the migration progress workflow needs-triage

Comments

@JCZuurmond
Copy link
Member

JCZuurmond commented Sep 11, 2024

Add a cli command create-ucx-catalog to create a catalog called ucx that is available (for read and write) to all workspaces

@github-project-automation github-project-automation bot moved this to Triage in UCX Sep 11, 2024
@JCZuurmond JCZuurmond changed the title Create a ucx catalog via a cli-command [FEATURE] Create a ucx catalog via a cli-command Sep 11, 2024
@JCZuurmond JCZuurmond added needs-triage feat/migration-progress Issues related to the migration progress workflow labels Sep 12, 2024
@JCZuurmond JCZuurmond self-assigned this Sep 19, 2024
@JCZuurmond JCZuurmond moved this from Triage to Active Backlog in UCX Sep 19, 2024
@asnare
Copy link
Contributor

asnare commented Sep 23, 2024

This also needs to be part of the assign-metastore command. The idea is that we want this (and #2572) to happen as soon as possible once a metastore has been attached, and the assign-metastore command is the most convenient place to ensure that this happens.

Currently some customers will be (externally) assigning the metastore, so as part of this we will need to:

  • Update the assign-metastore command to ensure that it's a no-op if a metastore has already been assigned to the workspace (or all in the collection).
  • Update the documentation to mention that this is a mandatory step in the migration.

@asnare
Copy link
Contributor

asnare commented Sep 23, 2024

Another requirement, given the metastore can be shared across multiple workspaces is that the catalog may already exist: this is anticipated, and shouldn't be an error.

@nfx nfx closed this as completed in #2694 Sep 25, 2024
nfx pushed a commit that referenced this issue Sep 25, 2024
## Changes
Add `create-ucx-catalog` cli command to create the catalog (going to be)
used for migration tracking (possibly) accross multiple workspaces.

### Linked issues

Resolves #2571

### Functionality

- [x] added relevant user documentation
- [x] added new CLI command: `create-ucx-catalog`

### Tests

- [x] manually tested
- [x] added unit tests
- [x] added integration tests

---------

Co-authored-by: Andrew Snare <asnare@users.noreply.github.com>
@github-project-automation github-project-automation bot moved this from Active Backlog to Archive in UCX Sep 25, 2024
jgarciaf106 pushed a commit to rportilla-databricks/ucx that referenced this issue Sep 26, 2024
## Changes
Add `create-ucx-catalog` cli command to create the catalog (going to be)
used for migration tracking (possibly) accross multiple workspaces.

### Linked issues

Resolves databrickslabs#2571

### Functionality

- [x] added relevant user documentation
- [x] added new CLI command: `create-ucx-catalog`

### Tests

- [x] manually tested
- [x] added unit tests
- [x] added integration tests

---------

Co-authored-by: Andrew Snare <asnare@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feat/migration-progress Issues related to the migration progress workflow needs-triage
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants