Skip to content

fix: name space imports should not change project #1515

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.

Sign up for GitHub

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

Merged
matttrach merged 5 commits into from
Jun 9, 2025
Merged

fix: name space imports should not change project #1515

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
84c0d56
fix: name space imports should not change project
matttrach May 22, 2025
98ecfcd
fix: error importing name space with mismatch
matttrach May 27, 2025
8c06906
fix: add environment variables for CI
matttrach May 27, 2025
2f6dfcb
fix: update docs
matttrach May 27, 2025
fd60840
fix: Merge changes from branch 'master'
matttrach May 30, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/resources/namespace.md
View file
Open in desktop
Comment thread
matttrach marked this conversation as resolved.
Original file line number Diff line number Diff line change
Expand Up @@ -134,8 +134,8 @@ Namespaces can be imported using the namespace ID in the format `<project_id>.<n
$ terraform import rancher2_namespace.foo &lt;project_id&gt;.&lt;namespaces_id&gt;
```

`<project_id>` is in the format `<cluster_id>:<id>`, but <id> part is optional:
`<project_id>` is in the format `<cluster_id>:<id>`, this is the output from `data.rancher2_cluster.downstream_cluster.default_project_id`

- If full project_id is provided, `<project_id>=<cluster_id>:<id>`, the namespace'll be assigned to corresponding cluster project once it's imported.
- If `<id>` part is omitted `<project_id>=<cluster_id>`, the namespace'll not be assigned to any project. To move it into a project, `<project_id>=<cluster_id>:<id>` needs to be updated in tf file. Namespace movement is only supported inside same `cluster_id`.
The `<project_id>` must match the actual resource, importing will error on project mismatch.

In past versions you could modify the namespace while importing it, this functionality is no longer available.
Loading