Skip to content

Allow giving no env prefix#326

Merged
Nexucis merged 1 commit intomainfrom
fix/noprefix
Feb 27, 2026
Merged

Allow giving no env prefix#326
Nexucis merged 1 commit intomainfrom
fix/noprefix

Conversation

@celian-garcia
Copy link
Member

I noticed that if we specify no prefix, the env variable taken should be in format "_FIELD1" instead of just "FIELD1".
This PR is here to fix it.

Signed-off-by: Celian GARCIA <celian.garcia@amadeus.com>
@Nexucis
Copy link
Member

Nexucis commented Feb 27, 2026

while I agree on the fix, I am wondering why you would end up by not giving a prefix actually.

@celian-garcia
Copy link
Member Author

Personally, in some tests. But also I can imagine that someone deployed in a k8s pod don't see the point of prefixing if the environment is already scoped in a container.

@celian-garcia
Copy link
Member Author

This is not a strong requirements, just I feel not elegant to have _ prefix by default.

Copy link
Member

@Nexucis Nexucis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah I agree, if the code allows to have no prefix, then it should be handled correctly.
Thank you for the fix and the explanation on how you found this one.

@Nexucis Nexucis merged commit 51fd796 into main Feb 27, 2026
6 checks passed
@Nexucis Nexucis deleted the fix/noprefix branch February 27, 2026 13:19
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