Repository provider retruning HTTP response status 404 error when resources exist
#1140
Comments
|
We also encounter this issue. We are running on terraform provider version 11.6.0 - to me it looks like this is not a problem of the provider, but a problem of Artifactory itself? |
|
@Osazz @Junkern Thanks for the report. This issue is introduced by The Artifactory engineering team is working on a fix/patch. I don't have a ETA or release version yet. Once I know, I'll pass it on here. |
|
I am also seeing this issue on Artifactory version 7.77.5. Specifically when trying to use the |
|
See my debug log below: Expand for more infoSample code used to generate the aboveresource "platform_group" "my-group" {
name = "my-group"
description = "My group"
auto_join = true
admin_privileges = false
}
resource "artifactory_managed_user" "test-user" {
name = "test-user"
password = "dcfsdcfsdcsdcsdZ!£"
email = "[email protected]"
groups = [platform_group.my-group.name]
}
resource "platform_permission" "my-permission" {
name = "my-permission-name"
artifact = {
actions = {
groups = [
{
name = platform_group.my-group.name
permissions = ["READ", "WRITE"]
}
]
}
targets = [
{
name = "test-repo"
include_patterns = ["**"]
}
]
}
} |
|
@zamanh Please create an issue in the Platform repo. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I have a docker remote and virtual repository been managed by Terraform. (resource has been created).
Time to modify something as easy as the description and Terraform is retuning a
HTTP response status 404:Failed to execute add project resource with error Could not find projecterror.This behaviour is confirmed for both remote and virtual docker repository and Conan remote repository
Even though terraform failed, modification was still applied in the artifactory
Version Information
Artifactory: 7.101.2
Terraform : 1.9.8
Terraform provider Version: 12.5.1
Terraform Error
More Debug log maybe this will be helpful
More Debug Log
The text was updated successfully, but these errors were encountered: