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

Project transfer failing with --noop #725

Closed
long-wan-ep opened this issue Apr 9, 2024 · 0 comments · Fixed by #726
Closed

Project transfer failing with --noop #725

long-wan-ep opened this issue Apr 9, 2024 · 0 comments · Fixed by #726
Labels

Comments

@long-wan-ep
Copy link
Contributor

Describe the bug

The project: transfer_from config is failing when run with --noop, if there are project_settings defined in the config. This is due to the project_settings processor getting a 404 when trying to fetch the settings from GitLab API(since the project doesn't get moved in dry-run).

GitLabForm version

Output of gitlabform -V

🏗 GitLabForm version: 3.9.3 = the latest stable 😊

GitLab version

v16.9.2-ee

@amimas amimas added the 🐛bug label Apr 11, 2024
amimas pushed a commit that referenced this issue Apr 12, 2024
…ther additional configs (#726)

The `project: transfer_from` config fails when run with `--noop`, if there are other configurations for the project (i.e. `project_settings`). This is due to the `project_settings` processor getting a 404 when trying to fetch the settings from GitLab API(since the project doesn't get moved in dry-run).

The dry-run/noop logic is updated to account for situation when project transfer configuration is used. Additional relevant test cases have been included as well.

Fixes #725
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
2 participants