sva.sentinelone
This collection provides several unofficial ansible modules and roles to use with SentinelOne management consoles (by svalabs)
overview
Collections overview, how to request a namespace (by ansible-collections)
sva.sentinelone | overview | |
---|---|---|
1 | 12 | |
10 | 246 | |
- | 1.2% | |
5.9 | 3.7 | |
9 days ago | 9 days ago | |
Python | ||
GNU General Public License v3.0 only | GNU General Public License v3.0 only |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
sva.sentinelone
Posts with mentions or reviews of sva.sentinelone.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-12-02.
-
The Bullhorn #83 (Ansible Newsletter)
Hey Ansible Community! Colleagues and I developed some Ansible Modules for configuring SentinelOne Management Consoles and we bundled them into an Ansible collection sva.sentinelone. We would like to have some community feedback and maybe some of you have SentinelOne in use and would like to manage your environment with our collection. You can find the collection on Ansible Galaxy or Github.
overview
Posts with mentions or reviews of overview.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-12-12.
-
The Bullhorn #84 (Ansible Newsletter)
As mentioned in last week's Bullhorn issue, cyberark.pas is subject to removal from version 9 of the Ansible community package due to unresolved Collection Requirements violations. A week has passed since the community-topics issue was filed and other SC members confirmed the violation, so a vote has been started (vote ends on 2022-12-16).
-
The Bullhorn #83 (Ansible Newsletter)
cyberark.pas is subject to removal from version 9 of the Ansible community package due to unresolved Collection Requirements violations. Please see community-topics#168 for more information.
-
The Bullhorn #80 (Ansible Newsletter)
The community steering committee has started a vote on whether we should amend the Ansible community package removal process to consider collections with unresolved Collection Requirements violations unmaintained and thus subject to removal. Please see the PR that amends the policy and the community-topics ticket for more information.
-
The Bullhorn #79 (Ansible Newsletter)
The Ansible Community Steering Committee has approved a change to the Collection Requirements re. SCM and release requirements. Collections were always required to tag releases, but we have clarified what tagging actually means. We have also explicitly stated that "collection artifacts released to Galaxy MUST be built from the sources that are tagged in the collection's git repository as that release." Please see the full change for more information.
-
The Bullhorn #69 (Ansible Newsletter)
We are happy to announce that the ibm.spectrum_virtualize collection has been included in the ansible community package. Thanks to everyone who helped review the collection and thanks to the maintainers for submitting the collection and making it satisfy the Collection requirements!
-
The Bullhorn #62 (Ansible Newsletter)
How? Copy the Review checklist into a discussion and go through it. See the complete example.
-
The Bullhorn #56 (Ansible Newsletter)
We've recently signed off on that process, which you can review here.
-
The Bullhorn #55 (Ansible Newsletter)
Your votes needed! Proposal: merge and adopt the procedures defined in Describe how collections can be removed from the Ansible package. Please vote in this issue (and not in the PR). The vote will close on 2022-04-27.
-
Future of Ansible package
Pros: - Motivation for developers to create new collections which can become a part of Ansible package ("so popular and important in IT world", etc). - Motivation to create content satisfying the collection requirements. - Motivation to maintain included collections to avoid kicking them out from the package "I can't show off with my collection any more..:(" - ...(suggest yours)
-
The Bullhorn #49 (Ansible Newsletter)
We have docs in three places today for contributors: * ansible/ansible in the community folder * ansible/community-docs - more collection focused * ansible-collections/overview - has deeper collection contribution details