fix: allow empty secret values when setting secrets from .env file

[shashwat-dixit]

Fixes #87

Description

Problem:

• When running infisical secrets set --file .env, if any secret has an empty value, the CLI prints "Secret key 'X' has an empty value" and exits
• The message is ambiguous - unclear if it's an error, warning, or info
• The entire operation fails and no secrets are set
• This is inconsistent with the Infisical UI which allows empty values

Solution:

• Remove the restriction that blocks empty secret values
• Display an informational warning when empty values are detected
• Continue processing and set all secrets from the file
• Only block on empty keys (which are invalid), not empty values

Changes:

• packages/util/secrets.go: Replace PrintErrorMessageAndExit with warning message for empty values
• packages/util/secrets.go: Update validation to only check for empty keys

Type

• Bug fix
• New feature
• Improvement
• Breaking change
• Documentation

Tests

• Created .env file with empty value (KEY1=value1, KEY2=, KEY3=value3)
• Verified all secrets are set successfully
• Verified warning is displayed for empty value
• Verified existing functionality still works for non-empty values

---

• I have read the contributing guide, agreed and acknowledged the code of conduct. 📝

[greptile-apps]

Greptile Summary

This PR fixes a usability issue where the CLI rejected empty secret values, even though the Infisical UI allows them. The changes convert the error into a warning, allowing the operation to continue.

Changes:

• Line 655: Changed PrintErrorMessageAndExit to PrintWarning when an empty value is detected during file parsing
• Line 708: Removed the empty value check (|| splitKeyValueFromArg[1] == "") from validation, now only validates that keys are non-empty
• Fixed typo: "none empty" → "non empty" in error message

Impact:

• Users can now set secrets with empty values via .env file, matching UI behavior
• Empty keys remain blocked (correct behavior)
• Operation continues and sets all valid secrets instead of failing entirely

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The changes are straightforward and well-scoped: converting an error to a warning for empty secret values, and removing the corresponding validation check. This aligns the CLI behavior with the UI, which already allows empty values. The change only affects empty values (not empty keys, which remain blocked), and the validation logic is correctly preserved for other critical checks.
• No files require special attention

Important Files Changed

Filename	Overview
packages/util/secrets.go	Changed empty value validation from error to warning, now allows empty secret values to match UI behavior

[greptile-apps]

Greptile found no issues!

From now on, if a review finishes and we haven't found any issues, we will not post anything, but you can confirm that we reviewed your changes in the status check section.

_{This feature can be toggled off in your Code Review Settings by deselecting "Create a status check for each PR".}