Assigned
Status Update
Comments
wr...@google.com <wr...@google.com> #2
Hi, could you please share screen shots of the UI you refer? Currently in the Cloud Source Repositories UI, in the top you will find:
YourRepository > Branch > file
You have a drop down in Repository and in Branch to change anytime.
Description
When pushing to Artifact Registry while using WIF attributes there is a possibility of receiving a 400 error with the following message:
"That's an error. Your client has issued a malformed or illegal request. That's all we know."
This issue is caused by the WIF attributes. When using too many of them it can cause issues with the URL in the GCP backend resulting in the above error.
What you expected to happen:
For customers to be able to push to Artifact Registry using all of their desired WIF attributes.
Steps to reproduce:
1. Push to Artifact Registry with no WIF and receive a successful response.
2. Add WIF attributes mappings with approximately 2000 bytes of dummy text and receive 400 error.
Other information (workarounds you have tried, documentation consulted, etc):
As a workaround customers can reduce the length of their WIF attribute mappings, or until a fix is implemented they can push to Artifact Registry without WIF attributes.