Support AAP 2.5

[ryancbutler]

Since AAP 2.5 uses a different API path the provider will need to handle the multiple paths depending on version. I see a test already exists for this but the provider only handles /api/ and not the newer /controller/api found in 2.5

[srlynch1]

The code here is actually committed to dynamically calculate the correct api end points. Nothing needs to be statically configured.

Suggest perhaps just cutting a new release we made zero changes and it's fully functional just with a new provider build with your existing code as this was already committed post 1.0 release.

[Sokren]

Hello,
I have the same issue with the AAP provider available on Terraform, and it is not finding the correct path for version 2.5.
Here are some screenshots showing the problem.

[ryancbutler]

As a workaround, I forked the repo and adjusted the API pathing https://registry.terraform.io/providers/ryancbutler/aap/latest

[srlynch1]

You don't need to change the API pathing, dynamic pathing is already in place and works regardless if 2.4 or 2.5.

Red Hat just need to release a new provider build. The PR was already merged here #30

[ryancbutler]

The code here is actually committed to dynamically calculate the correct api end points. Nothing needs to be statically configured.

Suggest perhaps just cutting a new release we made zero changes and it's fully functional just with a new provider build with your existing code as this was already committed post 1.0 release.

Sorry to bump. But is this a possible request? Would help out a lot with our 2.5 deployment.

[GomathiselviS]

Thank you for reporting the issue. The new version of terraform-provider-aap, which will include support for dynamic pathing, will be released soon.