eu-fr2 region not recognized during apply

[Naimabdelkefi]

Affected modules

• devsecops_ci_toolchain
• devsecops_cd_toolchain
• devsecops_cc_toolchain

Terraform CLI and Terraform provider versions

• Terraform version:
• Provider version:

Terraform output

Error occurred while configuring Toolchain service: "service URL for region 'eu-fr2' not found"

Debug output

2025/08/26 07:20:25 Terraform plan | summary: 'Error occurred while configuring Toolchain service: "service URL for region
2025/08/26 07:20:25 Terraform plan |   ''eu-fr2'' not found"'
2025/08/26 07:20:25 Terraform plan | severity: error
2025/08/26 07:20:25 Terraform plan | resource: ibm_cd_toolchain
2025/08/26 07:20:25 Terraform plan | operation: read
2025/08/26 07:20:25 Terraform plan | component:
2025/08/26 07:20:25 Terraform plan |   name: github.com/IBM-Cloud/terraform-provider-ibm
2025/08/26 07:20:25 Terraform plan |   version: 1.79.1
2025/08/26 07:20:25 Terraform plan |   with module.terraform_devsecops_alm.module.devsecops_ci_toolchain[0].ibm_cd_toolchain.toolchain_instance,
2025/08/26 07:20:25 Terraform plan |   on .terraform/modules/terraform_devsecops_alm.devsecops_ci_toolchain/main.tf line 305, in resource "ibm_cd_toolchain" "toolchain_instance":
2025/08/26 07:20:25 Terraform plan |  305: resource "ibm_cd_toolchain" "toolchain_instance" {

Expected behavior

Toolchains should be created successfully in the eu-fr2 region

Actual behavior

The module works as expected in the eu-de region for example. However, when switching to eu-fr2, terraform apply fails in IBM Schematics with a region not found error.

Steps to reproduce (including links and screen captures)

1. Use the module terraform-ibm-devsecops-alm
2. set all toolchain regions (toolchain_region, ci_toolchain_region, cd_toolchain_region, cc_toolchain_region) to eu-fr2.
3. Run terraform apply in IBM Schematics.

Anything else

Until recently, we were testing with version v2.8.1 of the terraform-ibm-devsecops-alm module. We also tried upgrading to the latest version (v2.8.7), but it did not resolve the issue.
Initially, we were unaware that the environment variable IBMCLOUD_TOOLCHAIN_ENDPOINT needed to be explicitly set for the eu-fr2 region. After opening a support case with IBM, we learned about this requirement and tried the following:

1. Using endpoints.json and provider configuration
   Following this documentation: Custom Service Endpoints, we updated our provider.tf:

And created endpoints.json at the root of the repo:

We tested different combinations of visibility (public, private) and endpoint keys, but all resulted in the same error:
Error occurred while configuring Toolchain service: "service URL for region 'eu-fr2' not found"
or
Error occurred while configuring Toolchain service: "service URL for region 'BNPP_EU'
2. Setting the environment variable in Schematics
We also tried the second method mentioned in IBM's documentation: setting the environment variable directly in the Schematics workspace settings:
IBMCLOUD_TOOLCHAIN_ENDPOINT=https://api.eu-fr2.devops.cloud.ibm.com/toolchain/v2
This allowed terraform plan to succeed, but terraform apply still failed with the same region error.

---

By submitting this issue, you agree to follow our Code of Conduct

[Naimabdelkefi]

Update
Following our support case with IBM Cloud, we received confirmation that the issue with endpoints_file_path in the IBM Terraform provider has been resolved in version 1.82.0.
However, we are currently unable to test this fix because the terraform-ibm-devsecops-alm module is locked to provider version 1.79.2, as defined in its version.tf:

terraform {
  required_providers {
    ibm = {
      source  = "IBM-Cloud/ibm"
      version = "1.79.2"
    }
  }
}

Attempting to run terraform init with the newer provider results in the following error:

Error: Failed to query available provider packages

Could not retrieve the list of available versions for provider ibm-cloud/ibm: locked provider registry.terraform.io/ibm-cloud/ibm 1.79.1 does not 
match configured version constraint >= 1.70.0, 1.79.1, 1.82.0, < 2.0.0; must use terraform init -upgrade to allow selection of new versions

To see which modules are currently depending on ibm-cloud/ibm and what versions are specified, run the following command:
    terraform providers

We kindly ask the maintainers to consider reviewing the strict version constraint on the IBM provider in the module, to allow compatibility with newer releases such as 1.82.0, which resolve critical issues like the one described here.

[huayuenh]

Addressed in this PR #614

[ibrawaneba-sys]

Hi,
Sorry but we have tried to deploy with 1.82.0 version of the provider, but still getting errors.
It can't find the ''pipeline'' variable in the following resources : ci_pipeline_instance, cd_pipeline_instance and pr_pipeline_instance.

Please find below the error logs :

 Error: ---
 id: terraform-e06847ff
 summary: 'CreateTektonPipelineWithContext failed: ''pipeline'' not found.'
 severity: error
 resource: ibm_cd_tekton_pipeline
 operation: create
 component:
   name: github.com/IBM-Cloud/terraform-provider-ibm
   version: 1.82.0
 ---
 

   with module.terraform_devsecops_alm.module.devsecops_ci_toolchain[0].module.pipeline_pr[0].ibm_cd_tekton_pipeline.pr_pipeline_instance,
   on .terraform/modules/terraform_devsecops_alm.devsecops_ci_toolchain/pipeline-pr/pipeline-pr.tf line 1, in resource "ibm_cd_tekton_pipeline" "pr_pipeline_instance":
    1: resource "ibm_cd_tekton_pipeline" "pr_pipeline_instance" {

[huayuenh]

We're looking at some updates and additional steps to work around this until a better solution is available. Will get an update out soon

[lionelmace]

@huayuenh any update?

[huayuenh]

We just made a release yesterday that will allow for the deploying to eu-fr2, using the new toolchain_resource_region_override variable and setting the appropriate additional env vars.
v2.8.14

[huayuenh]

• First
  export IBMCLOUD_TOOLCHAIN_ENDPOINT=https://api.eu-fr2.devops.cloud.ibm.com/v2
  export IBMCLOUD_TEKTON_PIPELINE_ENDPOINT=https://devops-api.eu-fr2.devops.cloud.ibm.com/v2

• Then you can apply the following tfvars

---

ibmcloud_api_key. =
toolchain_resource_group = "Default"
toolchain_region = "us-south" #Set any valid region to satisfy the Terraform Provider validation. It will be overridden with the above set env vars

toolchain_resource_region_override = "eu-fr2" # set the region for where all the resources will actually be created.
toolchain_name = "23-sept-kube-da"

sm_name = "Secrets Manager"
sm_location = "eu-fr2"
sm_resource_group = "Default"
sm_secret_group = "Default"

#there are two ways to set the pipeline properties for ci,cd and cc. A path can be set to a json file containing the pipeline properties

ci_pipeline_properties_filepath="./solutions/kubernetes/ci-properties.json"
cd_pipeline_properties_filepath="./solutions/kubernetes/cd-properties.json"
cc_pipeline_properties_filepath="./solutions/kubernetes/cc-properties.json"

• alternatively
• the json content be set directly into these variables . Needs to be stringified

ci_pipeline_properties =
cd_pipeline_properties =
cc_pipeline_properties =

---

See https://github.com/terraform-ibm-modules/terraform-ibm-devsecops-alm/tree/main/solutions/kubernetes for the example pipeline json files

[ibrawaneba-sys]

Hi, We have tested this version but we face a new issue :

Error: ---
 2025/09/23 15:16:50 Terraform apply | id: terraform-464044d4
 2025/09/23 15:16:50 Terraform apply | summary: **'CreateTektonPipelineWithContext failed: Forbidden'**
 2025/09/23 15:16:50 Terraform apply | severity: error
 2025/09/23 15:16:50 Terraform apply | resource: ibm_cd_tekton_pipeline
 2025/09/23 15:16:50 Terraform apply | operation: create
 2025/09/23 15:16:50 Terraform apply | component:
 2025/09/23 15:16:50 Terraform apply |   name: github.com/IBM-Cloud/terraform-provider-ibm
 2025/09/23 15:16:50 Terraform apply |   version: 1.82.0
 2025/09/23 15:16:50 Terraform apply | ---
 2025/09/23 15:16:50 Terraform apply | 
 2025/09/23 15:16:50 Terraform apply | 
 2025/09/23 15:16:50 Terraform apply |   with module.terraform_devsecops_alm.module.devsecops_cd_toolchain[0].module.pipeline_cd.ibm_cd_tekton_pipeline.cd_pipeline_instance,
 2025/09/23 15:16:50 Terraform apply |   on .terraform/modules/terraform_devsecops_alm.devsecops_cd_toolchain/pipeline-cd/pipeline-cd.tf line 1, in resource "ibm_cd_tekton_pipeline" "cd_pipeline_instance":
 2025/09/23 15:16:50 Terraform apply |    1: resource "ibm_cd_tekton_pipeline" "cd_pipeline_instance" {

Best Regards

[huayuenh]

Hi, We have tested this version but we face a new issue :

Error: ---
 2025/09/23 15:16:50 Terraform apply | id: terraform-464044d4
 2025/09/23 15:16:50 Terraform apply | summary: **'CreateTektonPipelineWithContext failed: Forbidden'**
 2025/09/23 15:16:50 Terraform apply | severity: error
 2025/09/23 15:16:50 Terraform apply | resource: ibm_cd_tekton_pipeline
 2025/09/23 15:16:50 Terraform apply | operation: create
 2025/09/23 15:16:50 Terraform apply | component:
 2025/09/23 15:16:50 Terraform apply |   name: github.com/IBM-Cloud/terraform-provider-ibm
 2025/09/23 15:16:50 Terraform apply |   version: 1.82.0
 2025/09/23 15:16:50 Terraform apply | ---
 2025/09/23 15:16:50 Terraform apply | 
 2025/09/23 15:16:50 Terraform apply | 
 2025/09/23 15:16:50 Terraform apply |   with module.terraform_devsecops_alm.module.devsecops_cd_toolchain[0].module.pipeline_cd.ibm_cd_tekton_pipeline.cd_pipeline_instance,
 2025/09/23 15:16:50 Terraform apply |   on .terraform/modules/terraform_devsecops_alm.devsecops_cd_toolchain/pipeline-cd/pipeline-cd.tf line 1, in resource "ibm_cd_tekton_pipeline" "cd_pipeline_instance":
 2025/09/23 15:16:50 Terraform apply |    1: resource "ibm_cd_tekton_pipeline" "cd_pipeline_instance" {

Best Regards

Could you check if you have a Continuous Delivery service setup ? https://cloud.ibm.com/catalog/services/continuous-delivery

[ibrawaneba-sys]

Thank you @huayuenh we successfully deployed without any errors.

[vburckhardt]

Hi @huayuenh - could we close this one if complete?