Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[web/ingress] unable to set nginx.ingress.kubernetes.io/use-regex using CLI #552

Open
1 of 3 tasks
nbr opened this issue Nov 21, 2022 · 1 comment
Open
1 of 3 tasks

Comments

@nbr
Copy link
Contributor

nbr commented Nov 21, 2022

Description

The use-regex annotation is expected to be either "true" or "false" by the ingress controller.

I'm able to successfully set the annotation in the browser, but cannot do so using the CLI with a values.yaml file such as:

ingress:
  annotations:
    nginx.ingress.kubernetes.io/use-regex: "true"
...

The following error message is printed:

Error: Upgrade failed: template: web/templates/ingress.yaml:48:21: executing "web/templates/ingress.yaml" at <eq $v "null">: error calling eq: incompatible types for comparison

It seems like "true" is being coerced into a bool and failing here according to the above error.

Location

  • Browser
  • CLI
  • API

Steps to reproduce

  1. Set ingress.annotations["nginx.ingress.kubernetes.io/use-regex"] = "true"
  2. Run porter update config --app=my-app --values=values.yaml

Additional details

Setting ingress.annotations["nginx.ingress.kubernetes.io/use-regex"] = true fails at the ingress controller both locally and in the browser with the following message:

Error: Upgrade failed: unable to decode "": json: cannot unmarshal bool into Go struct field ObjectMeta.metadata.annotations of type string

@mnafees
Copy link
Contributor

mnafees commented Jan 11, 2023

Hi @nbr, thank you for reporting this. The team is working on a fix. I'll update you here once the fix is up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants