Closed rarkins closed 1 year ago
The autoReplace function appears to recognize the "depName mismatch" however the final update still has that mismatch. Maybe the file/branch was not reset correctly after the second update or something similar.
Or maybe we need the replaceString
to be shorter somehow
What about if a manager can return a replace regex hint, so autoreplace can use that to replace in replacestring? 🤔
ah, i see, the sample depname is somehow confusing. instead of 111111111111.dkr.ecr.us-east-1.amazonaws.com/my-repository
it should be 222222222222.dkr.ecr.us-east-1.amazonaws.com/my-repository
otherwise 111111111111.dkr.ecr.us-east-1.amazonaws.com/my-repository
would be replace to 4211111111111.dkr.ecr.us-east-1.amazonaws.com/my-repository
. because regex manager replaces first occurence?
@viceice yeah, that leading set of 1's is a bit misleading. Here's a number that is more correct in my context (while still not disclosing anything sensitive).
883407545824.dkr.ecr.us-east-1.amazonaws.com/my-repository
became
883407545824.dkr.ecr.us-east-42.amazonaws.com/my-repository
I dont have an account with 1's in the AWS account portion....but if the code was replacing my 1 in us-east-1, then I wouldn't be surprised (now) to also see it replace the leading 1's. Maybe it's enough for my issue to suggest it was replacing all instances of the current value instead of the one that was specifically the tag (after the colon)
@rarkins @viceice - I think this may be resolved now. WDYT?
Originally posted by @caphrim007 in https://github.com/renovatebot/renovate/discussions/8054#discussioncomment-221190