falcosecurity/falco

Update docs for Puppet module

genebean opened this issue · 7 comments

What to document

https://forge.puppet.com/modules/sysdig/falco still points to this repo but it seems that something related to #1114 moved it to https://github.com/falcosecurity/evolution/tree/master/integrations/puppet-module/falco.

That code seems to have been abandoned and is in a non-working state. I have taken the code and created https://github.com/voxpupuli/puppet-falco. I suggest updating your docs to point to it and marking the one in falcosecurity/evolution as depreciated via https://forgeapi.puppet.com/#tag/Module-Operations/operation/deprecateModule

What do you think about proposing your up-to-date module to be adopted as sandbox project, in falcosecurity/evolution?

Depends on what that means. Puppet modules can't be used effectively when embedded within another repo, but if that isn't a requirement I'd like to know more.

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.

In response to this:

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

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.