Alex Hung

@jckos `property_sets` attribute is supported in all the repository resources. For example, the local repository: https://registry.terraform.io/providers/jfrog/artifactory/latest/docs/resources/local#property_sets

@jckos Ah, now I understand. No, the `property_sets` attribute doesn't create new property set. There's no support for creating new property sets in the provider.

Related to #329 and https://github.com/jfrog/terraform-provider-project/issues/27

@OSapozhnikov Sorry for taking this long to get to this ticket. What you are seeing is a function of how Terraform and Artifactory works unfortunately. So the sequence of events...

@martinm82 I have not been able to reproduce this issue. I am able to create a project with no `repos` and then create a local repo with `project_key`. Then after...

@martinm82 Our local dev install script increment the patch version automatically, even without any code change. 2.20.0 is released version which is what I used to test

@martinm82 You're right. Updating an existing repo with `project_key` doesn't assign to the project. Looks like an Artifactory API bug. The provider calls the [repo update API](https://www.jfrog.com/confluence/display/JFROG/Artifactory+REST+API#ArtifactoryRESTAPI-UpdateRepositoryConfiguration) with project key...

@martinm82 An alternative is to add the repo key to `project.repos` list in HCL. This will assign existing repos to that project.

> Should this issue be tracked in a separate issue? Let's continue tracking problem #1 with this issue. @dasmanas is working on problem #2. We can create a separate issue...

@martinm82 @dasmanas See https://github.com/jfrog/terraform-provider-project/issues/27