WIP: [TRACKING] Falco 1.0 items

[leogr]

Motivation

We recently published the high-level roadmap for Falco 1.0. Although we don't have a target date yet, we already have some items around, planned for 1.0, that directly affect the Falco application. This issue only aims to track these items/issues.

A dedicated GitHub issue is available only for deprecations we may want to introduce in Falco 1.0

Falco 1.0.0 items

Beta Give feedback

1. [TRACKING] Breaking changes in Falco 1.0.0 #3038
   kind/documentation +1
   

   
2. OCI artifacts and the rules files have different names rules#211
   kind/feature +1
   
3. [TRACKING] Rules syntax enhancements (backward-compatible) #3255
   1 of 4
   kind/feature +1
   
4. [UMBRELLA] Streamlining falco.yaml structure #3254
   2 of 3
   kind/feature +1
   
5. [Proposal] Streamlining docker images #3165
   kind/feature +1
   

   
6. [TRACKING] metrics framework future refactors / cleanups #3194
   kind/feature lifecycle/stale +2
   
7. Follow CLI args standards in Falco #3049
   kind/feature +1
   
8. Improve rule files validity checking #1332
   area/engine area/rules help wanted kind/feature lifecycle/stale +5
   
9. Semantic of container.id and container.name libs#2057
   kind/feature +1
10. double qoute in rule's condition is not working as expected #1859
    area/rules kind/bug +2
    

[leogr]

/milestone 1.0.0
/assign

[poiana]

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

[leogr]

/remove-lifecycle stale