Closed steakunderscore closed 1 year ago
I think this is actually a misunderstanding of how bash sourcing works. I hadn't realised that calling . falco-driver-loader --source-only
actually sets the environment variables in the current shell. Perhaps there's scope to update the docs for documenting how this flag can be used instead.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen
.
Mark the issue as fresh with /remove-lifecycle rotten
.
Provide feedback via https://github.com/falcosecurity/community. /close
@poiana: Closing this issue.
Describe the bug
I believe
falco-driver-loader --source-only
seems like it should expose bash variables somehow. However it's current behaviour is synonymous withecho ""
.How to reproduce it Call
(note there's no output above)
Expected behaviour
Something like:
Environment
Additional context