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

distribution release fails due to "Configuration file doesn't exists" #879

Closed
pkissling opened this issue Jan 9, 2025 · 4 comments · Fixed by #885
Closed

distribution release fails due to "Configuration file doesn't exists" #879

pkissling opened this issue Jan 9, 2025 · 4 comments · Fixed by #885

Comments

@pkissling
Copy link

pkissling commented Jan 9, 2025

Describe the bug
In my CI I want to release a distribution from the command line without using a crowdin.yml file.
Although I provide all required arguments on the command line, the CLI fails with message "Configuration file doesn't exist. Run the 'crowdin init' to generate configuration skeleton". For all other commands i can provide all arguments from the command line without the need to create a crowdin.yml file

To Reproduce
Steps to reproduce the behavior:

$ crowdin distribution release <hash> --token=<token> --base-url=<base-url> --project-id=<project-id>
❌ Configuration file doesn't exist. Run the 'crowdin init' to generate configuration skeleton

If instead, i provide an invalid crowdin config file (see below), i get a warning but the distribution is still released properly.

$ echo '{}' > crowdin_dummy.json && crowdin distribution release <hash> --token=<token> --base-url=<base-url> --project-id=<project-id> --config=crowdin_dummy.json
⚠️  File '~/Coding/work/some-project/crowdin_dummy.json' is not a YAML or YML file
⚠️  File '~/Coding/work/some-project/crowdin_dummy.json' is not a YAML or YML file
✔️  Fetching project info     
✔️  Releasing distribution (100%)
✔️  Distribution '<hash>' has been successfully released

**Expected behavior**
I'd expect to be able to use `crowdin distribution release` without providing the `--config` argument if i provide all other mandatory arguments on the command line.

**Environment:**
 - OS: macOS 15.1.1
 - CLI Version: 4.5.0
@yevheniyJ yevheniyJ linked a pull request Jan 11, 2025 that will close this issue
@lukasreussner
Copy link
Contributor

@pkissling This should be fixed now.

@andrii-bodnar
Copy link
Member

@lukasreussner It's not released yet. I'm in the process of releasing a new version.

@andrii-bodnar
Copy link
Member

Available in 4.5.1.

@pkissling
Copy link
Author

Fix is working as expected. Thank you for addressing this so quickly.

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 a pull request may close this issue.

3 participants