You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The DockerRepositorySettingsImpl class does not include a setter (or getter) for the dockerTagRetention property. This value can be set via the UI and is present in the getRepository data, so it's a valid / active field with no was to set it through the ArtifactoryClient.
To Reproduce
Code examination of org.jfrog.artifactory.client.model.repository.settings.impl.DockerRepositorySettingsImpl
Expected behavior
There should be a setter for dockerTagRetention which will then set the value as provided ( an Integer ) which is then reflected whn the docker repository is created.
Screenshots
N/A
Versions
Artifactory Java Client version: 2.11.1
Operating system: N/A
Artifactory Version: N/A
Additional context
This is a key issue as it's not allowing me to fully configure docker federated repositories through the Artifactory Client, forcing me to rely on default values that I may not want.
The text was updated successfully, but these errors were encountered:
Describe the bug
The DockerRepositorySettingsImpl class does not include a setter (or getter) for the dockerTagRetention property. This value can be set via the UI and is present in the getRepository data, so it's a valid / active field with no was to set it through the ArtifactoryClient.
To Reproduce
Code examination of org.jfrog.artifactory.client.model.repository.settings.impl.DockerRepositorySettingsImpl
Expected behavior
There should be a setter for dockerTagRetention which will then set the value as provided ( an Integer ) which is then reflected whn the docker repository is created.
Screenshots
N/A
Versions
Additional context
This is a key issue as it's not allowing me to fully configure docker federated repositories through the Artifactory Client, forcing me to rely on default values that I may not want.
The text was updated successfully, but these errors were encountered: