Ability to expose terrakube service with custom path

[dawidmalina]

Feature description 💡

I see that we can configure: .Values.ingress.api.path, .Values.ingress.registry.path and .Values.ingress.dex.path but not sure how to configure custom path for particular service.

If we would be able to expose api under /api and registry under /registry potentially we could use only one domain instead of three different ones.

Anything else?

No response

[alfespa17]

Hello @dawidmalina

The API and Registry require to be in the root.

I explained that a little bit in this issue, it is restriction when using the Terraform/tofu cli and the well known endpoint.

#452 (comment)

[alfespa17]

For the ingress configuration you could check the default values here

https://github.com/AzBuilder/terrakube-helm-chart/blob/a1526fe5e3e35dc8a1f12ed6dcce87afc394f2fa/charts/terrakube/values.yaml#L226

In the helm chart repository there is one folder with a couple of examples too

[dawidmalina]

Thank you for the explanation. I am not familiar with terraform endpoints but /.well-known/terraform.json returns different values (api, registry) or exactly same in this case? You are using nginx as web (ui) and with nginx we can do almost everything :)

[alfespa17]

The endpoint expose different terraform protocols.

The API expose the login.v1, state.v2, tfe.v2 that are use use when you do a terraform login and when you use the Terraform remote state and cloud block information.

The registry expose the login.v1, modules.v1 and providers.v1 information those are used when the Terraform CLI downloads modules and providers

The response content is different as you can see in the image from the comment in the other issue

[dawidmalina]

@alfespa17 i just check what endpoints are exposed with tfe and from what I see they are using one front (domain):

• modules.v1: /api/registry/v1/modules/
• providers.v1: /api/registry/v1/providers/
• state.v2: /api/v2/
• tfe.v2: api/v2/
• tfe.v2.1: /api/v2/
• tfe.2.2: /api/v2/
• versions.v1: https://checkpoint-api.hashicorp.com/v1/versions/

Could we use similar approach?

[alfespa17]

@alfespa17 i just check what endpoints are exposed with tfe and from what I see they are using one front (domain):

• modules.v1: /api/registry/v1/modules/
• providers.v1: /api/registry/v1/providers/
• state.v2: /api/v2/
• tfe.v2: api/v2/
• tfe.v2.1: /api/v2/
• tfe.2.2: /api/v2/
• versions.v1: https://checkpoint-api.hashicorp.com/v1/versions/

Could we use similar approach?

It could work like that in the future, but right now it will require some refactor in the code to change the responses of the well known endpoint and other internal logic inside the registry and the executor I think