dopplerhq / secrets-fetch-action Goto Github PK

Hello Doppler friends!

I am in the process of moving some CI workflows to Github Actions and like the simplicity of this action vs installing & running doppler run in CI.

But, we use Doppler as a general configuration management tool (as outlined in the Doppler docs here). This means we have values like NODE_ENV=test in Doppler. When these are pulled in, we get rather silly output such as:

Starting "rush ci:***"
Analyzing repo state... DONE (0.***8 seconds)

Would it be possible for y'all to to skip the core.setSecret call for values that are unmasked? Even adding this as an optional input parameter so we can decide would be awesome.

The 31st of May 2023, when the set-output command is going to get disabled is getting near. I can see that you already resolved this in the latest commits, but the current 1.1.0 release, still has this problem. Any plans to release a new version?

https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

I've encountered a deprecation warning while using the dopplerhq/[email protected] action. The warning states that Node.js 16 actions are deprecated, and it recommends an update to Node.js 20. Here's the warning message I received:

Node.js 16 actions are deprecated.
Please update the following actions to use Node.js 20: dopplerhq/[email protected].
For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/

The files that seem to be affected are:

• https://github.com/DopplerHQ/secrets-fetch-action/blob/main/.github/workflows/test.yml#L12
• https://github.com/DopplerHQ/secrets-fetch-action/blob/main/action.yml#L25