if an existing codeartifact upstream repository is deleted and its references in another repository is deleted from terraform and applied, the action should be complete.
Actual Behavior
We did not have any issue with npm and nuget upstreams, and we hadnt even created a maven upstream. But we discovered the issue with Maven/Gradle. The autogenerated maven-metadata.xml started showing:
A repository referenced in your upstream graph no longer exists. To fix this issue, use the UpdateRepository API with your new desired upstream configuration. Note that if an upstream repository was deleted and recreated using the same name, UpdateRepository must still be called to reference the new repository. This issue may be present in any repository in the upstream graph.
And of course builds were not working.
So I had to actually call update-repository to register the deletion.
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
Volunteering to Work on This Issue
If you are interested in working on this issue, please leave a comment.
If this would be your first contribution, please review the contribution guide.
Terraform Core Version
1.4.5
AWS Provider Version
3.75.2
Affected Resource(s)
No response
Expected Behavior
if an existing codeartifact upstream repository is deleted and its references in another repository is deleted from terraform and applied, the action should be complete.
Actual Behavior
We did not have any issue with npm and nuget upstreams, and we hadnt even created a maven upstream. But we discovered the issue with Maven/Gradle. The autogenerated maven-metadata.xml started showing:
And of course builds were not working. So I had to actually call update-repository to register the deletion.
Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
after creating them, get rid of the upstreams....
Steps to Reproduce
aws codeartifact update-repository --domain myDomain --repository myRepoInUse
Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
None