Error on `API_TOKEN_PEPPERS` dictionary key type

[Atomicbeast101]

The Helm chart version

7.4.0

Environment Versions

Kubernetes: 1.33.2
Helm: 4.1.0
Netbox: 4.5.1

Custom chart values

extraConfig:
  - values:
      API_TOKEN_PEPPERS:
        1: $(netboxPepperKey01)

Current Behavior & Steps to Reproduce

Run helm chart install/update as normal.

Helm chart's generated configuration.yml show's this value for API_TOKEN_PEPPERS:

 extra-0.yaml: |-
    API_TOKEN_PEPPERS:
      "1": j5Qco6h1G9RxewjSozff9eRLzQtQoCBtLCNNFcIR95snxGSqoz

You can see that 1 value gets converted to "1" which is an issue because API_TOKEN_PEPPERS require that key to be an integer and not a string. Netbox documentation on this: https://netboxlabs.com/docs/netbox/configuration/required-parameters/#api_token_peppers

Expected Behavior

Error logs to not state that key is a string and not integer.

Helm chart's generated configmap/app-netbox manifest file to contain this instead:

 extra-0.yaml: |-
    API_TOKEN_PEPPERS:
      1: j5Qco6h1G9RxewjSozff9eRLzQtQoCBtLCNNFcIR95snxGSqoz

or something similar that keeps the key 1 as integer instead of string.

NetBox Logs

django.core.exceptions.ImproperlyConfigured: Invalid API_TOKEN_PEPPERS key: 1. All keys must be integers.

[LeoColomb]

Thanks for filing this issue, @Atomicbeast101.
Indeed, the behaviours described matches the expectations on how the template should result.
Have you tried the following?

extraConfig:
  - values:
      API_TOKEN_PEPPERS: |-
        1: $(netboxPepperKey01)

[Atomicbeast101]

@LeoColomb Much appreciated for the suggestion. I've tried a different ways to get it to properly convert to a dictionary with integer-based key and cannot seem to get it to work:

1st try:

extraConfig:
  - values:
      API_TOKEN_PEPPERS: |-
        1: $(netboxPepperKey01)

returns

  extra-0.yaml: |-
    API_TOKEN_PEPPERS: 1: j5Qco6h1G9RxewjSozff9eRLzQtQoCBtLCNNFcIR95snxGSqoz

2nd try:

extraConfig:
  - values:
      API_TOKEN_PEPPERS: |-
        { 1: '$(netboxPepperKey01)' }

returns

  extra-0.yaml: |-
    API_TOKEN_PEPPERS: '{ 1: ''j5Qco6h1G9RxewjSozff9eRLzQtQoCBtLCNNFcIR95snxGSqoz'' }'

3rd try:

extraConfig:
  - values:
      API_TOKEN_PEPPERS: |-
        { 1: $(netboxPepperKey01) }

returns

  extra-0.yaml: |-
    API_TOKEN_PEPPERS: '{ 1: j5Qco6h1G9RxewjSozff9eRLzQtQoCBtLCNNFcIR95snxGSqoz }'

It keeps returning this error log:

django.core.exceptions.ImproperlyConfigured: API_TOKEN_PEPPERS must be a dictionary.

Which is expected as it should look like this instead:

  extra-0.yaml: |-
    API_TOKEN_PEPPERS:
        1: j5Qco6h1G9RxewjSozff9eRLzQtQoCBtLCNNFcIR95snxGSqoz

or

  extra-0.yaml: |-
    API_TOKEN_PEPPERS: { 1: 'j5Qco6h1G9RxewjSozff9eRLzQtQoCBtLCNNFcIR95snxGSqoz' }

[LeoColomb]

After trying other workarounds and reconsidering this behavior, I have made a PR to the NetBox app to help with processing YAML configuration. netbox-community/netbox#21351