Giter VIP home page Giter VIP logo

skydive's Introduction

Skydive Ansible Collection

Ansible Collection for the Skydive network / protocols analyzer.

skydive's People

Contributors

adrianlzt avatar andersson007 avatar ansible-zuul[bot] avatar capttrews avatar gundalow avatar lebauce avatar pabelanger avatar

Stargazers

avatar avatar avatar

Watchers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Forkers

pabelanger capttrews datadope-io lebauce andersson007

skydive's Issues

Inclusion of skydive.skydive in Ansible 2.10

This collection will be included in Ansible 2.10 because it contains modules and/or plugins that were included in Ansible 2.9. Please review:

DEADLINE: 2020-08-18

The latest version of the collection available on August 18 will be included in Ansible 2.10.0, except possibly newer versions which differ only in the patch level. (For details, see the roadmap). Please release version 1.0.0 of your collection by this date! If 1.0.0 does not exist, the same 0.x.y version will be used in all of Ansible 2.10 without updates, and your 1.x.y release will not be included until Ansible 2.11 (unless you request an exception at a community working group meeting and go through a demanding manual process to vouch for backwards compatibility . . . you want to avoid this!).

Follow semantic versioning rules

Your collection versioning must follow all semver rules. This means:

  • Patch level releases can only contain bugfixes;
  • Minor releases can contain new features, new modules and plugins, and bugfixes, but must not break backwards compatibility;
  • Major releases can break backwards compatibility.

Changelogs and Porting Guide

Your collection should provide data for the Ansible 2.10 changelog and porting guide. The changelog and porting guide are automatically generated from ansible-base, and from the changelogs of the included collections. All changes from the breaking_changes, major_changes, removed_features and deprecated_features sections will appear in both the changelog and the porting guide. You have two options for providing changelog fragments to include:

  1. If possible, use the antsibull-changelog tool, which uses the same changelog fragment as the ansible/ansible repository (see the documentation).
  2. If you cannot use antsibull-changelog, you can provide the changelog in a machine-readable format as changelogs/changelog.yaml inside your collection (see the documentation of changelogs/changelog.yaml format).

If you cannot contribute to the integrated Ansible changelog using one of these methods, please provide a link to your collection's changelog by creating an issue in https://github.com/ansible-community/ansible-build-data/. If you do not provide changelogs/changelog.yml or a link, users will not be able to find out what changed in your collection from the Ansible changelog and porting guide.

Make sure your collection passes the sanity tests

Run ansible-test sanity --docker -v in the collection with the latest ansible-base or stable-2.10 ansible/ansible checkout.

Keep informed

Be sure you're subscribed to:

Questions and Feedback

If you have questions or want to provide feedback, please see the Feedback section in the collection requirements.

(Internal link to keep track of issues: ansible-collections/overview#102)

Important information for collection maintainers

SUMMARY

Dear maintainers,

This is important for your collections!

  • In accordance with the Community decision, we have created the news-for-maintainers repository for announcements of changes impacting collection maintainers (see the examples) instead of Issue 45 that will be closed soon.

    • To keep yourself well-informed and, therefore, things in your collection working, please subscribe to the repository by using the Watch button in the upper right corner on the repository's home page.
    • If you do not want to get notifications about related discussions, please subscribe only to Issues.
    • Please read the brief guidelines on how the repository should be used.
    • Please avoid unnecessary discussions in issues, use the Discussions feature. Every comment posted will notify a lot of folks!

  • Also we would like to remind you about the Bullhorn contributor newsletter which has recently started to be released weekly. To learn what it looks like, see the past releases. Please subscribe and talk to the Community via Bullhorn!

  • Join us in #ansible-social (for news reporting & chat), #ansible-community (for discussing collection & maintainer topics), and other channels on Matrix/IRC.

  • Help the Community and the Steering Committee to make right decisions by taking part in discussing and voting on the Community Topics that impact the whole project and the collections in particular. Your opinion there will be much appreciated!

Thank you!

Ansible Contributor Summit. Tuesday, April 12, 2022.

Ansible Contributor Summit

We are happy to announce that the registration for the Ansible Contributor Summit is open!

Why

  • This is a great opportunity for interested people to meet, discuss related topics, share their stories and opinions, get the latest important updates and just to hang out together.

  • There will be different announcements & presentations by Community, Core, Cloud, Network, and other teams.

  • Current contributors will be happy to share their stories and experience with newcomers.

  • There will be links to interactive self-passed instruqt scenarios shared during the event that help newcomers learn different aspects of development.

Where/when

Online on Matrix and Youtube. Tuesday, April 12, 2022, 12:00 - 20:00 UTC.

How to join

  • Add the event to your calendar. Use the ical URL (for example, in Google Calendar "Add other calendars" > "Import from URL") instead of importing the .ics file so that any updates to the event will be reflected in your calendar.

  • Check out the Summit page:

    • Add you name to attendees.
    • Suggest summit topics that would be interesting to you to hear about.
    • Vote on and propose changes to topics suggested by others.
    • If you want to be a presenter, please contact the Ansible Community team via [email protected].

We are looking forward to seeing you!:)

Add integration tests

SUMMARY

Add integration tests.

Activate those tests in the github workflow.

ISSUE TYPE
  • Feature Idea

Consider using true/false for all booleans in docs

Based on the community decision to use true/false for boolean values in documentation and examples, we ask that you evaluate booleans in this collection and consider changing any that do not use true/false (lowercase).

See documentation block format for more info (specifically, option defaults).

If you have already implemented this or decide not to, feel free to close this issue.

P.S. This is auto-generated issue, please raise any concerns here

Private argument spec validation methods no longer available in Ansible Core 2.11

SUMMARY

Argument spec validation has changed in Ansible Core 2.11. The following private method calls should be changed to use the public interface:

collections/skydive/plugins/module_utils/network/skydive/api.py
131:                metadata = module._check_type_dict(params["metadata"])  # --> ansible.module_utils.common.validation.check_type_dict()
ISSUE TYPE
  • Bug Report
COMPONENT NAME

collections/skydive/plugins/module_utils/network/skydive/api.py

ANSIBLE VERSION
2.11

no_log provider password

SUMMARY

provider.password should be marked as no_log to avoid printing the password in debug mode.

ISSUE TYPE
  • Bug Report
COMPONENT NAME

plugins/doc_fragments/skydive.py

Important information for collection maintainers

SUMMARY

Dear maintainers,

This is important for your collections!

  • In accordance with the Community decision, we have created the news-for-maintainers repository for announcements of changes impacting collection maintainers (see the examples) instead of Issue 45 that will be closed soon.

    • To keep yourself well-informed and, therefore, things in your collection working, please subscribe to the repository by using the Watch button in the upper right corner on the repository's home page.
    • If you do not want to get notifications about related discussions, please subscribe only to Issues.
    • Please read the brief guidelines on how the repository should be used.
    • Please avoid unnecessary discussions in issues, use the Discussions feature. Every comment posted will notify a lot of folks!

  • Also we would like to remind you about the Bullhorn contributor newsletter which has recently started to be released weekly. To learn what it looks like, see the past releases. Please subscribe and talk to the Community via Bullhorn!

  • Join us in #ansible-social (for news reporting & chat), #ansible-community (for discussing collection & maintainer topics), and other channels on Matrix/IRC.

  • Help the Community and the Steering Committee to make right decisions by taking part in discussing and voting on the Community Topics that impact the whole project and the collections in particular. Your opinion there will be much appreciated!

Thank you!

Move 'master' branch to 'main'

Following the Ansible guidelines:

All new repositories under `ansible-collections <https://github.com/ansible-collections>`_ MUST have ``main`` as the default branch.

Existing repositories SHOULD be converted to use ``main``

Move to API REST

Currently this module is using the websockets API to connect to the skydive analyzer.

Now that API REST is available I think it makes more sense to use that one, as this use case does not need a permanent connection neither receiving data pushed from the server.

Sanity tests failing in community.skydive

SUMMARY

We are running sanity tests across every collection included in the Ansible community package (as part of this issue) and found that ansible-test sanity --docker against community.skydive 1.0.0 fails with ansible-core 2.13.0rc1 in ansible 6.0.0a2.

ISSUE TYPE
  • Bug Report
COMPONENT NAME

n/a

ANSIBLE VERSION
ansible [core 2.13.0rc1]
COLLECTION VERSION
1.0.0
STEPS TO REPRODUCE
ansible-test sanity --docker
EXPECTED RESULTS

Tests are either passing or ignored.

ACTUAL RESULTS
ERROR: Found 1 future-import-boilerplate issue(s) which need to be resolved:
ERROR: plugins/module_utils/network/skydive/api.py:0:0: missing: from __future__ import (absolute_import, division, print_function)
ERROR: Found 1 metaclass-boilerplate issue(s) which need to be resolved:
ERROR: plugins/module_utils/network/skydive/api.py:0:0: missing: __metaclass__ = type
ERROR: Found 56 validate-modules issue(s) which need to be resolved:
ERROR: plugins/lookup/skydive.py:0:0: invalid-documentation: DOCUMENTATION.lookup: extra keys not allowed @ data['lookup']. Got 'skydive'
ERROR: plugins/lookup/skydive.py:0:0: invalid-documentation: DOCUMENTATION.name: required key not provided @ data['name']. Got None
ERROR: plugins/modules/skydive_capture.py:0:0: doc-missing-type: Argument 'capture_name' in argument_spec uses default type ('str') but documentation doesn't define type
ERROR: plugins/modules/skydive_capture.py:0:0: doc-missing-type: Argument 'description' in argument_spec uses default type ('str') but documentation doesn't define type
ERROR: plugins/modules/skydive_capture.py:0:0: doc-missing-type: Argument 'endpoint' in argument_spec found in provider uses default type ('str') but documentation doesn't define type
ERROR: plugins/modules/skydive_capture.py:0:0: doc-missing-type: Argument 'interface_name' in argument_spec uses default type ('str') but documentation doesn't define type
ERROR: plugins/modules/skydive_capture.py:0:0: doc-missing-type: Argument 'password' in argument_spec found in provider uses default type ('str') but documentation doesn't define type
ERROR: plugins/modules/skydive_capture.py:0:0: doc-missing-type: Argument 'query' in argument_spec uses default type ('str') but documentation doesn't define type
ERROR: plugins/modules/skydive_capture.py:0:0: doc-missing-type: Argument 'state' in argument_spec uses default type ('str') but documentation doesn't define type
ERROR: plugins/modules/skydive_capture.py:0:0: doc-missing-type: Argument 'type' in argument_spec uses default type ('str') but documentation doesn't define type
ERROR: plugins/modules/skydive_capture.py:0:0: doc-missing-type: Argument 'username' in argument_spec found in provider uses default type ('str') but documentation doesn't define type
ERROR: plugins/modules/skydive_capture.py:0:0: doc-required-mismatch: Argument 'endpoint' in argument_spec found in provider is not required, but is documented as being required
ERROR: plugins/modules/skydive_capture.py:0:0: invalid-ansiblemodule-schema: AnsibleModule.argument_spec.capture_name.ib_req: extra keys not allowed @ data['argument_spec']['capture_name']['ib_req']. Got True
ERROR: plugins/modules/skydive_capture.py:0:0: invalid-ansiblemodule-schema: AnsibleModule.argument_spec.description.ib_req: extra keys not allowed @ data['argument_spec']['description']['ib_req']. Got True
ERROR: plugins/modules/skydive_capture.py:0:0: invalid-ansiblemodule-schema: AnsibleModule.argument_spec.extra_tcp_metric.ib_req: extra keys not allowed @ data['argument_spec']['extra_tcp_metric']['ib_req']. Got True
ERROR: plugins/modules/skydive_capture.py:0:0: invalid-ansiblemodule-schema: AnsibleModule.argument_spec.interface_name.ib_req: extra keys not allowed @ data['argument_spec']['interface_name']['ib_req']. Got True
ERROR: plugins/modules/skydive_capture.py:0:0: invalid-ansiblemodule-schema: AnsibleModule.argument_spec.ip_defrag.ib_req: extra keys not allowed @ data['argument_spec']['ip_defrag']['ib_req']. Got True
ERROR: plugins/modules/skydive_capture.py:0:0: invalid-ansiblemodule-schema: AnsibleModule.argument_spec.layer_key_mode.ib_req: extra keys not allowed @ data['argument_spec']['layer_key_mode']['ib_req']. Got True
ERROR: plugins/modules/skydive_capture.py:0:0: invalid-ansiblemodule-schema: AnsibleModule.argument_spec.query.ib_req: extra keys not allowed @ data['argument_spec']['query']['ib_req']. Got True
ERROR: plugins/modules/skydive_capture.py:0:0: invalid-ansiblemodule-schema: AnsibleModule.argument_spec.reassemble_tcp.ib_req: extra keys not allowed @ data['argument_spec']['reassemble_tcp']['ib_req']. Got True
ERROR: plugins/modules/skydive_capture.py:0:0: invalid-ansiblemodule-schema: AnsibleModule.argument_spec.type.ib_req: extra keys not allowed @ data['argument_spec']['type']['ib_req']. Got True
ERROR: plugins/modules/skydive_capture.py:0:0: no-log-needed: Argument 'layer_key_mode' in argument_spec could be a secret, though doesn't have `no_log` set
ERROR: plugins/modules/skydive_capture.py:0:0: nonexistent-parameter-documented: Argument 'user' found in provider is listed in DOCUMENTATION.options, but not accepted by the module argument_spec
ERROR: plugins/modules/skydive_capture.py:0:0: parameter-type-not-in-doc: Argument 'provider' in argument_spec defines type as 'dict' but documentation doesn't define type
ERROR: plugins/modules/skydive_capture.py:0:0: undocumented-parameter: Argument 'username' found in provider is listed in the argument_spec, but not documented in the module documentation
ERROR: plugins/modules/skydive_edge.py:0:0: doc-missing-type: Argument 'endpoint' in argument_spec found in provider uses default type ('str') but documentation doesn't define type
ERROR: plugins/modules/skydive_edge.py:0:0: doc-missing-type: Argument 'password' in argument_spec found in provider uses default type ('str') but documentation doesn't define type
ERROR: plugins/modules/skydive_edge.py:0:0: doc-missing-type: Argument 'state' in argument_spec uses default type ('str') but documentation doesn't define type
ERROR: plugins/modules/skydive_edge.py:0:0: doc-missing-type: Argument 'username' in argument_spec found in provider uses default type ('str') but documentation doesn't define type
ERROR: plugins/modules/skydive_edge.py:0:0: doc-required-mismatch: Argument 'endpoint' in argument_spec found in provider is not required, but is documented as being required
ERROR: plugins/modules/skydive_edge.py:0:0: nonexistent-parameter-documented: Argument 'user' found in provider is listed in DOCUMENTATION.options, but not accepted by the module argument_spec
ERROR: plugins/modules/skydive_edge.py:0:0: parameter-type-not-in-doc: Argument 'child_node' in argument_spec defines type as 'str' but documentation doesn't define type
ERROR: plugins/modules/skydive_edge.py:0:0: parameter-type-not-in-doc: Argument 'host' in argument_spec defines type as 'str' but documentation doesn't define type
ERROR: plugins/modules/skydive_edge.py:0:0: parameter-type-not-in-doc: Argument 'metadata' in argument_spec defines type as 'dict' but documentation doesn't define type
ERROR: plugins/modules/skydive_edge.py:0:0: parameter-type-not-in-doc: Argument 'parent_node' in argument_spec defines type as 'str' but documentation doesn't define type
ERROR: plugins/modules/skydive_edge.py:0:0: parameter-type-not-in-doc: Argument 'provider' in argument_spec defines type as 'dict' but documentation doesn't define type
ERROR: plugins/modules/skydive_edge.py:0:0: parameter-type-not-in-doc: Argument 'relation_type' in argument_spec defines type as 'str' but documentation doesn't define type
ERROR: plugins/modules/skydive_edge.py:0:0: undocumented-parameter: Argument 'username' found in provider is listed in the argument_spec, but not documented in the module documentation
ERROR: plugins/modules/skydive_node.py:0:0: doc-missing-type: Argument 'endpoint' in argument_spec found in provider uses default type ('str') but documentation doesn't define type
ERROR: plugins/modules/skydive_node.py:0:0: doc-missing-type: Argument 'host' in argument_spec uses default type ('str') but documentation doesn't define type
ERROR: plugins/modules/skydive_node.py:0:0: doc-missing-type: Argument 'metadata' in argument_spec uses default type ('str') but documentation doesn't define type
ERROR: plugins/modules/skydive_node.py:0:0: doc-missing-type: Argument 'name' in argument_spec uses default type ('str') but documentation doesn't define type
ERROR: plugins/modules/skydive_node.py:0:0: doc-missing-type: Argument 'node_type' in argument_spec uses default type ('str') but documentation doesn't define type
ERROR: plugins/modules/skydive_node.py:0:0: doc-missing-type: Argument 'password' in argument_spec found in provider uses default type ('str') but documentation doesn't define type
ERROR: plugins/modules/skydive_node.py:0:0: doc-missing-type: Argument 'seed' in argument_spec uses default type ('str') but documentation doesn't define type
ERROR: plugins/modules/skydive_node.py:0:0: doc-missing-type: Argument 'state' in argument_spec uses default type ('str') but documentation doesn't define type
ERROR: plugins/modules/skydive_node.py:0:0: doc-missing-type: Argument 'username' in argument_spec found in provider uses default type ('str') but documentation doesn't define type
ERROR: plugins/modules/skydive_node.py:0:0: doc-required-mismatch: Argument 'endpoint' in argument_spec found in provider is not required, but is documented as being required
ERROR: plugins/modules/skydive_node.py:0:0: invalid-ansiblemodule-schema: AnsibleModule.argument_spec.host.ib_req: extra keys not allowed @ data['argument_spec']['host']['ib_req']. Got True
ERROR: plugins/modules/skydive_node.py:0:0: invalid-ansiblemodule-schema: AnsibleModule.argument_spec.metadata.ib_req: extra keys not allowed @ data['argument_spec']['metadata']['ib_req']. Got True
ERROR: plugins/modules/skydive_node.py:0:0: invalid-ansiblemodule-schema: AnsibleModule.argument_spec.name.ib_req: extra keys not allowed @ data['argument_spec']['name']['ib_req']. Got True
ERROR: plugins/modules/skydive_node.py:0:0: invalid-ansiblemodule-schema: AnsibleModule.argument_spec.node_type.ib_req: extra keys not allowed @ data['argument_spec']['node_type']['ib_req']. Got True
ERROR: plugins/modules/skydive_node.py:0:0: invalid-ansiblemodule-schema: AnsibleModule.argument_spec.seed.ib_req: extra keys not allowed @ data['argument_spec']['seed']['ib_req']. Got True
ERROR: plugins/modules/skydive_node.py:0:0: nonexistent-parameter-documented: Argument 'user' found in provider is listed in DOCUMENTATION.options, but not accepted by the module argument_spec
ERROR: plugins/modules/skydive_node.py:0:0: parameter-type-not-in-doc: Argument 'provider' in argument_spec defines type as 'dict' but documentation doesn't define type
ERROR: plugins/modules/skydive_node.py:0:0: undocumented-parameter: Argument 'username' found in provider is listed in the argument_spec, but not documented in the module documentation
ERROR: The 3 sanity test(s) listed below (out of 43) failed. See error output above for details.
future-import-boilerplate
metaclass-boilerplate
validate-modules
ERROR: Command "podman exec ansible-test-controller-8gsmqslr /usr/bin/env ANSIBLE_TEST_CONTENT_ROOT=/root/ansible_collections/community/skydive LC_ALL=en_US.UTF-8 /usr/bin/python3.10 /root/ansible/bin/ansible-test sanity --containers '{}' --skip-test pylint --metadata tests/output/.tmp/metadata-c8bxf2l9.json --truncate 0 --color no --host-path tests/output/.tmp/host-2_cjpfe9" returned exit status 1.

rename repo skydive.skydive

SUMMARY

Hi, can we please rename the repo to be consistent with others under gh/anisble-collections?

GitHub will maintain redirects. Once done we should review README and galaxy.yml

I assume Zuul config will also need updating

Unmaintained collection: Removal from Ansible (communtiy) package

It looks like this collection is effectively unmaintained. According to the current community guidelines for collections, we will consider removing it in a future version of the Ansible community package. Please see Unmaintained collection: community.skydive for more information.

At least one month after this announcement appears here and on Bullhorn, the Ansible Community Steering Committee will vote on whether this collection is considered unmaintained and will be removed, or whether it will be kept. If it will be removed, this will happen earliest in Ansible 9.0.0. Please note that people can still manually install the collection with ansible-galaxy collection install community.skydive even when it has been removed from Ansible.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.