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

Enforce DEEPFENCE_FILE_SERVER_PORT to be a string #2331

Merged
merged 1 commit into from
Oct 5, 2024

Conversation

psych0d0g
Copy link
Contributor

ConfigMap in version "v1" cannot be handled as a ConfigMap: json: cannot unmarshal number into Go struct field ConfigMap.data of type string

due to the template not quoting the port for an external S3 instance, the configmap will not be able to be applied

add quoting to the value for the port

Fixes #

Changes proposed in this pull request:
add | quote to the template that pulls the port number from values

ConfigMap in version "v1" cannot be handled as a ConfigMap: json: cannot unmarshal number into Go struct field ConfigMap.data of type string

due to the template not quoting the port for an external S3 instance, the configmap will not be able to be applied

add quoting to the value for the port
@ramanan-ravi
Copy link
Collaborator

Thanks for the contribution @psych0d0g

@ramanan-ravi ramanan-ravi merged commit 329a590 into deepfence:release-2.3 Oct 5, 2024
3 checks passed
ramanan-ravi pushed a commit that referenced this pull request Oct 5, 2024
ConfigMap in version "v1" cannot be handled as a ConfigMap: json: cannot unmarshal number into Go struct field ConfigMap.data of type string

due to the template not quoting the port for an external S3 instance, the configmap will not be able to be applied

add quoting to the value for the port
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

Successfully merging this pull request may close these issues.

2 participants