A repository cannot be created directly inside a project environment according to current recommendations

[richardmcsong]

Given a repository that needs to be created inside an environment inside that project:

resource "project" "tenant" {
  key = "foo"
}

resource "project_environment" "myenv" {
  name        = "myenv"
  project_key = project.tenant.key
}

resource "artifactory_federated_docker_v2_repository" "repo" {
  name = "docker"
  project_environments = [project_environment.myenv.name]
  [...]
}

resource "project_repository" "repo" {
  key = artifactory_federated_docker_v2_repository.repo.key
  project_key = project.tenant.key
}

The documentation recommends that the repository be associated to a project through the project_repository resource. However, the environment association only exists within initial federated repo definition. This leads to this error:

  │ Error: {
  │   "errors" : [ {
  │     "status" : 400,
  │     "message" : "Undefined environment 'myenv' in the project 'default'\n"
  │   } ]
  │ }

where the environment is not found within the global scope (only the project scope).

What is the recommendation to directly create the repo within a project environment (without multiple PRs)?

[alexhung]

@richardmcsong Unfortunately the project_environments attribute is one current use case where you will need to perform terraform apply twice. Meaning, first apply without project_environments attribute defined. After project and repo are created and associated, then you can apply the project environments in second terraform apply.

This is a limitation of the REST API and we are aware of it.