Alex Hung

@utviklingstjenester Thanks for the suggestion, we'll take a look.

@mcaulifn Something else to keep in mind. The micro-service architecture (I know Artifactory is still somewhat monolithic) means that some of the states are not up-to-dated instantaneously. Currently there isn't...

@bmanuel Thanks for the request, we will add this to our schedule. We will likely add new attribute `allow_download_and_distribute_when_unavailable` to resource `xray_settings`.

@piotrminkina Please create a separate GitHub issue for your problem, and we'll investigate. Thanks.

@skyzyx The `artifactory_keypair` resource was migrated from the SDKv2 library to the new Framework library in [9.7.0](https://github.com/jfrog/terraform-provider-artifactory/blob/master/CHANGELOG.md#970-oct-18-2023-tested-on-artifactory-76814-with-terraform-cli-v161). The `id` field was never part of the public schema but it's a...

@skyzyx No, the fact that SDKv2 treats `id` attribute with special meaning was one of the thing HashiCorp team fixed in Framework. Now there is no special attribute and it's...

@skyzyx Sorry it's been a while since I last touch this. Do you still have the error message from `artifactory_keypair` when you upgrade? And how did you resolve the issue?...

@skyzyx I installed provider 6.37.0 and created a new key pair resource on my local Artifactory instance. Then I upgraded provider to 10.1.4, ran `terraform apply`, and got no error....

@emiledd-nbs I wasn't sure from reading previous messages here if you have HCL to create repos for this project at the same time as creating the watch? If so, you...

@Dragotic Thanks for the report, I've added this to our plan to investigate.