ansible-lint was updated and the GitHub
action did not pin the dependency, resulting
in the repository to fail sanity tests.
Updating the repository to adhere to new fatal
linter rules, but also pinning the linter to
prevent failures that may be unrelated to the
particular commit.
Updating usages for python3.8 to 3.9 as ansible-lint
is dropping support for 3.8.
Ansible-lint is required for Ansible collection
certification for Automation Hub.
gcsfuse had no metadata associated with it, failing
the Ansible Hub upload.
Updating the maintainers guide with updated intructions from
Ansible engineers.
Fixing linting issues, and adding the linter as a GitHub workflow
to ensure there are no regressions.
The client's List continues to be flakey. disabling until
the endpoint is stable.
Switching tests to use ansible 2.14, as 2.13 has issues with
spawning a docker container.
Upgrading the base python version as a consequence.
Removing the need for docker from unit tests, since that was failing
and also non-critical to run unit tests.
- Updating and documenting changelog creation process.
antsibull-changelog was chosen because it is the standard tooling
recommended by Ansible developers.
- Documenting the release process and several others so others can perform it in the
future.
- Updating the integration tests to test against 2.13, which the 1.1.0
final release will be certified for.
- Created changelog and update galaxy.yaml for 1.1.0-beta, which will be
the next release.
As a first step to rehabilitate the google.cloud repository,
adding actions to help ensure that the collection is still
passing tests as changes are merged.
Details:
- ansible-devel was not added to the matrix since it may
destablize the tests, primarily used to validate the collection.
- running sanity tests reported over 100+ issues, backlogged to #498
before turning those on.
