Open mikenikles opened 3 months ago
Oh hold on, TagSlugs
is commented out here and for other functions for that matter. This happened a year ago though 🤔. Does nobody use tags or is it a user error on my side 😅?!
@mikenikles we also facing same issue.
I followed up with the team shortly after my last comment above and they said they'd work on this in the next sprint. Hoping that'll still happen because it's the only deal breaker at the moment for me.
Here's a video walkthrough of my setup and what I see in the CLI.
https://github.com/user-attachments/assets/0814b171-2510-4b52-8609-9b8a8b55b3eb
Hey @mikenikles , this was removed because filtering used to happen on client side. We'll need to add support for filtering with tags via API so that it can be properly filtered by clients such as CLI. We'll provide updates once that is added here
Thanks for looking into that and providing an update.
I'll filter client-side for now as a workaround. If you have beta CLI releases let me know, happy to help test it once it's ready.
Once this PR is released @mikenikles, your issue should be addressed https://github.com/Infisical/infisical/pull/2242
@mikenikles Imported secrets cannot be filtered by tags at the moment. The above PR will tag all the secrets in a path thought
Awesome, thanks guys for your help. I'll keep an eye on the next release and will report back once I've had a chance to test it.
Is there potentially a backend change that needs to be rolled out besides the CLI version 0.28.5
?
The results I see with 0.28.5
are the same as before where the --tags
CLI flag didn't work.
platform on main [!]
❯ infisical -v
infisical version 0.28.5
platform on main [!]
❯ infisical --log-level info run --path="/platform/packages/website" --tags="shared" -- node -e "console.log(process.env.SHARED_ONE); console.log(process.env.WEBSITE_ONE); console.log(process.env.WEBSITE_TWO); console.log(process.env.NOT_SHARED_TWO)"
4:59PM INF Injecting 0 Infisical secrets into your application process
undefined
undefined
undefined
undefined
platform on main [!]
❯ infisical --log-level info run --tags="shared" -- node -e "console.log(process.env.SHARED_ONE); console.log(process.env.WEBSITE_ONE); console.log(process.env.WEBSITE_TWO); console.log(process.env.NOT_SHARED_TWO)"
4:59PM INF Injecting 0 Infisical secrets into your application process
undefined
undefined
undefined
undefined
platform on main [!]
❯ infisical --log-level info run --path="/platform/packages/website" -- node -e "console.log(process.env.SHARED_ONE); console.log(process.env.WEBSITE_ONE); console.log(process.env.WEBSITE_TWO); console.log(process.env.NOT_SHARED_TWO)"
4:59PM INF Injecting 2 Infisical secrets into your application process
undefined
W1
W2
undefined
Any command that includes --tags
results in 0 secrets injected.
Yes you also need to update the backend
Oh, I use app.infisical.com :). I was wondering if the backend change is already deployed in the Infisical prod environment.
I tested again with the v0.30.0
CLI release, but any command that includes --tags="..."
still injects 0 secrets. Are you guys able to reproduce the issue based on my video and see the correct secrets injected?
Describe the bug
I have the following folder structure:
service1
shared1
shared2
service1
requires all secrets stored in theservice1
folder. It also requires some secrets fromshared1
and some secrets fromshared2
. I added theshared
tag to the secrets that are shared withservice1
.To start
service1
, I use:This only imports the secrets from the
service1
folder, but not any of the secrets tagged withshared
.To Reproduce
Steps to reproduce the behavior:
service1
folder at the root with a secret in itshared1
folder at the root with two secrets in it. Tag one secret withshared
.shared2
folder at the root with two secrets in it. Tag one secret withshared
.infisical run --path="/service1" --tags=shared -- node
service1
and neither of theshared
secrets.Expected behavior
3 secrets are available.
service1
shared1
shared2
Screenshots
N/A
Platform you are having the issue on: Mac
Additional context
This happens in project
3ffa4095-f4aa-4440-bfc0-fe6fa86f8493
.