Skip to content
This repository has been archived by the owner on Jun 18, 2024. It is now read-only.

References not resolved #18

Open
devilmark84 opened this issue Sep 29, 2023 · 2 comments
Open

References not resolved #18

devilmark84 opened this issue Sep 29, 2023 · 2 comments

Comments

@devilmark84
Copy link

devilmark84 commented Sep 29, 2023

It's the first time I'm using Infisical (self-hosted via docker at the last version you released) and the infisical-node.

I tried to fetch all secrets from a given path (e.g. /) in which I have a secret containing a reference to another secret (e.g. https://${X_MY_HOST}).

If I use the infisical-cli this reference is resolved, but using the getAllSecrets or the simple getSecret using the same token, the reference is not resolved.

These are the options I passed to the getAllSecrets:

{
  environment,
  path: `/${service}`,
  attachToProcessEnv: false,
  includeImports: true,
}

I hope it's not a bug of the infisical-node package.

Thanks in advance

@maidul98
Copy link
Contributor

Hmm, strange, I thought we added reference support but it looks like it's not in the code base https://github.com/Infisical/infisical-node/blob/main/src/helpers/secrets.ts#L63

We'll try to add this to our next weeks sprint

@devilmark84
Copy link
Author

devilmark84 commented Sep 29, 2023

Thank you very much, I think this is a very important feature.
It's so strange that no one open this issue.
Looking forward for your next release as soon as you can.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants