Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.

Cant' Create Workspace dataform after connection dev Azure git provider

Hello , we are migrating from legacy dataform to GCP dataform , our git provider is Azure.
After Creation Repo Dataform and configurating the connection ssh with Azure , I can't create Workspace it gives me this error :
Erreur de requête API : Currently only ASCII characters are supported in branch names.
how can I fix this ? 

Solved Solved
0 2 443
1 ACCEPTED SOLUTION

The error message you're encountering indicates that the branch name in your Azure Git repository contains non-ASCII characters, which are not supported by Google Cloud Dataform. To resolve this issue, consider the following solutions:

  1. Rename the Branch Using Git Commands: The most straightforward solution is to rename the branch to use only ASCII characters. This can be done using Git commands. For example, you can rename a branch using git branch -m old_branch new_branch. After renaming, push the changes to your remote repository.

  2. Create a New Branch with an ASCII-only Name: If you prefer to retain the original branch name for historical or tracking purposes, you can create a new branch with an ASCII-only name. Then, merge the changes from the original branch into this new branch. This approach maintains the history and changes from the original branch while ensuring compatibility with Google Cloud Dataform.

  3. Avoid Encoding Non-ASCII Characters: While it's technically possible to encode non-ASCII characters in the branch name using methods like URL encoding, this practice is unconventional and can lead to further compatibility issues with other tools and systems. It's generally recommended to stick with simple ASCII characters for branch names.

After implementing these changes, you should be able to create the Workspace in Google Cloud Dataform without encountering the error message. Additionally, remember to:

  • Communicate Changes: If you're part of a team, inform all members about the branch name changes to avoid confusion or conflicts.
  • Check Other Elements: Ensure that other elements like repository names, file names, or directory names also adhere to the ASCII-only rule.
  • Consult Documentation: Review the documentation for both Google Cloud Dataform and Azure for any specific guidelines regarding Git integration and branch naming conventions.

View solution in original post

2 REPLIES 2

The error message you're encountering indicates that the branch name in your Azure Git repository contains non-ASCII characters, which are not supported by Google Cloud Dataform. To resolve this issue, consider the following solutions:

  1. Rename the Branch Using Git Commands: The most straightforward solution is to rename the branch to use only ASCII characters. This can be done using Git commands. For example, you can rename a branch using git branch -m old_branch new_branch. After renaming, push the changes to your remote repository.

  2. Create a New Branch with an ASCII-only Name: If you prefer to retain the original branch name for historical or tracking purposes, you can create a new branch with an ASCII-only name. Then, merge the changes from the original branch into this new branch. This approach maintains the history and changes from the original branch while ensuring compatibility with Google Cloud Dataform.

  3. Avoid Encoding Non-ASCII Characters: While it's technically possible to encode non-ASCII characters in the branch name using methods like URL encoding, this practice is unconventional and can lead to further compatibility issues with other tools and systems. It's generally recommended to stick with simple ASCII characters for branch names.

After implementing these changes, you should be able to create the Workspace in Google Cloud Dataform without encountering the error message. Additionally, remember to:

  • Communicate Changes: If you're part of a team, inform all members about the branch name changes to avoid confusion or conflicts.
  • Check Other Elements: Ensure that other elements like repository names, file names, or directory names also adhere to the ASCII-only rule.
  • Consult Documentation: Review the documentation for both Google Cloud Dataform and Azure for any specific guidelines regarding Git integration and branch naming conventions.

Hello , it works now , the problem that we have some old branchs that not adhere to the ASCII-only rule, we deleted these branchs , and now we can create workspaces 
Thanks