ARTIFACTORY: Reason why Removing/Modifying the properties on the distributed release bundle is not allowed

ARTIFACTORY: Reason why Removing/Modifying the properties on the distributed release bundle is not allowed

AuthorFullName__c
Ujwal Poovaiah
articleNumber
000006017
ft:sourceType
Salesforce
FirstPublishedDate
2024-01-29T15:10:39Z
lastModifiedDate
2024-01-29
VersionNumber
1

We may observe the below situations when we try to delete or remove the properties on distributed bundles or artifacts.

When we distribute a release bundle with a set of properties. After that, when we removed/changed a property on the file and redistributed the content again:-

  • The removed property was not removed on the edge Node or Target instance.
  • When we redistribute the bundle with modified properties, the value was added to the already existing one.
Question 1: Is this behavior intentional? If yes, what is the reason behind it?

Removing/modifying the properties is not allowed on a distributed artifact and it is an expected behavior. The logic behind it is that nobody (even upcoming release versions) can change the artifacts including the properties on the edge Node(the properties are part of the signature) and also it collides with the idea of immutability of the release bundle hence this is the reason where the properties is not allowed to be removed or modified on the distributed bundles.

Question 2: Is there a way to delete the properties that were added to a distribution release bundle?

No, The possible solution is only by removing the previous release bundle and distributing the new one in case there are any changes to the properties and values that are needed.