Closed hsiddiqui84 closed 6 months ago
This is what it looks like with artifactory_permission_target:
@hsiddiqui84 Thanks for the report! Looks like a bug in parsing the ANY_
repository type in the provider. I'll add this to our plan.
It seems when the repo appears selected correctly, the groups tab shows that repo resource type is not selected correctly:
However, it appears to be selected correctly with ANY_REMOTE as part of platform_permission:
@alexhung it seems using ANY_REMOTE is the right thing to do but it does not show up correctly on the repo permission target UI.
@hsiddiqui84 The correct value to use is without the underscore actually. The documentation is incorrect. Try ANY REMOTE
.
Describe the bug
Artifactory Cloud version: 7.78.1 Terraform version: 1.3.6 Artifactory provider version: 10.3.1 Platform provider version: 1.5.0
I replaced the deprecated resource artifactory_permission_target from the artifactory provider with the new resource platform_permission from the platform provider and the repo association looks incorrect on the UI.
Original HCL snippet with artifactory_permission_target:
New HCL snippet with platform_permission:
Using ANY_REMOTE does not select the correct repo as can be seen in this screenshot:
Requirements for and issue
curl
it at$host/artifactory/api/system/version
Expected behavior The repository should appear as Any Remote instead of ANY_REMOTE as part of the respective permission.