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

Accept a list of paths in ingress-repository chart #719

Open
dkekel opened this issue Jun 20, 2022 · 0 comments
Open

Accept a list of paths in ingress-repository chart #719

dkekel opened this issue Jun 20, 2022 · 0 comments

Comments

@dkekel
Copy link

dkekel commented Jun 20, 2022

Hello,

Do you see any issue in having a list of paths coming from values file in ingress-repository chart?

Instead of having only two pre-defined paths for repository and API explorer

paths:
      - path: {{ .Values.repository.ingress.path }}
        {{- if eq "true" (include "common.ingress.supportsPathType" .) }}
        pathType: Prefix
        {{- end }}
        backend: {{- include "common.ingress.backend" (dict "serviceName" $serviceName "servicePort" $servicePort "context" $) | nindent 10 }}
      - path: {{ .Values.apiexplorer.ingress.path }}
        {{- if eq "true" (include "common.ingress.supportsPathType" .) }}
        pathType: Prefix
        {{- end }}
        backend: {{- include "common.ingress.backend" (dict "serviceName" $serviceName "servicePort" $servicePort "context" $) | nindent 10 }}

The use-case would be to provide a possibility to limit the number of exposed APIs, or in other words to fine-grain which Alfresco APIs should be accessible on the external network.

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

1 participant