Open MrLuje opened 1 week ago
@MrLuje Thanks for the report. I've added this to our plan to investigate.
@MrLuje Just want to point out that destination
does not accept repository key as name
. It should be name of the edge node. See https://jfrog.com/help/r/jfrog-platform-administration-documentation/add-destinations
@MrLuje I am unable to reproduce your issue. Using your TF configuration (with modification to run on my local Artifactory instance), there is no plan change after apply
even using repo key in the destination.targets.name
.
@alexhung Thanks for checking. Maybe related to our artifactory version (v7.84.12), I'll try with an updated instance in the coming weeks.
Describe the bug Deleting a
platform_permission
destination (https://registry.terraform.io/providers/jfrog/platform/latest/docs/resources/permission#destination) property is not workingRequirements for and issue
curl
it at$host/artifactory/api/system/version
(self-hosted v7.84.12)Expected behavior Ability to manage
platform_permission
destinationsdestination
block and applyTerraform will perform the following actions:
platform_permission.test-reader will be updated in-place
~ resource "platform_permission" "test-reader" {
(1 unchanged attribute hidden)
}
Plan: 0 to add, 1 to change, 0 to destroy.