Helm chart using malformed DOT_REMOTE_CALL_SUBNET_BLACKLIST default

Open Beginner friendly
#32,331 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
65/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
helm
Domain
cloud, devops

Research direction

Open the Helm chart's default values.yaml and the StatefulSet template that populates DOT_REMOTE_CALL_SUBNET_BLACKLIST. Render or install the chart in a sandbox, verify that commas are preserved in the environment value, and confirm the malformed-address warning no longer appears.

Written by the indexing model from the issue text.

Description

Team : Platform Type : Defect
Problem Statement

the default value for remoteCallSubnetBlacklist: 169.254.169.254/32,127.0.0.1/32,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16 in the helm default values.yaml does not contain quotes around the string. This is causing it to be parsed as a list and when inserting it into the DOTREMOTECALLSUBNETBLACKLIST in the stateful set it is removing the commas and concatenating causing an invalid configuration. The fix is to put double quotes around the string to force it as a string value.

25-06-04T17:14:00.644706862Z 17:14:00.644  WARN  network.IPUtils - Could not parse [169.254.169.254/32127.0.0.1/3210.0.0.0/8172.16.0.0/12192.168.0.0/16]
Steps to Reproduce

A sandbox using the current version of helm will produce the following when trying to connect externally including sending an analytics event.

25-06-04T17:14:00.644706862Z 17:14:00.644 WARN network.IPUtils - Could not parse [169.254.169.254/32127.0.0.1/3210.0.0.0/8172.16.0.0/12192.168.0.0/16]

Acceptance Criteria

Ensure that the enironment is properly parsed with commas and error does not appear in the log

dotCMS Version

NA

Proposed Objective

Cloud Engineering

Proposed Priority

Please Select

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No response

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

Dominant language
Java
Stars
970
Forks
486
Avg merge
3d 2h
Merged PRs (30d)
164

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dotCMS/core

All issues in dotCMS/core

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.