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

Noisy POSIX warning #32

Closed
oschlegel opened this issue Mar 31, 2022 · 5 comments · Fixed by #33
Closed

Noisy POSIX warning #32

oschlegel opened this issue Mar 31, 2022 · 5 comments · Fixed by #33

Comments

@oschlegel
Copy link

Hi, i'm getting a lot of warnings from your action like "One of the secrets has a name that is not POSIX compliant...", because basically all my secrets are not POSIX compliant. But since the conversion behavior is already documented in the readme and works fine i think it would be ok to use a debug message instead of a warning, this way it can still help to analyze and track down issues but doesn't clutter the workflow logs.

@jbabala-costa
Copy link
Contributor

jbabala-costa commented Apr 8, 2022

Hi, I have exactly the same issue. Could we introduce flag to suppress such warnings?

@abhilash1in
Copy link
Owner

Will be fixed with release 2.1.0 (coming soon, today or tomorrow).

@sharat87
Copy link

Hey, looks like this warning is still there. Can you confirm if I'm doing something wrong here please?

Screenshot 2022-06-15 at 14 23 15

The variables do actually load and work fine though.

Thank you for your work.

@abhilash1in
Copy link
Owner

@sharat87 you need to set disable-warnings: true in order to disable and suppress POSIX warnings.

@sharat87
Copy link

Hey @abhilash1in, thanks for sharing that. But wouldn't that hide all POSIX warnings? Is it possible to just hide this one particular warning?

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 a pull request may close this issue.

4 participants