the previous fix had invalid syntax (hard to test against the
master branch until after push).
This syntax is documented as correct:
https://github.com/actions/runner/issues/950
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.
Ansible role tests were failing due to ansible-lint reporting
multiple errors.
Fixing those errors resolves the failing tests.
Switching gcsfuse to use gcloud's bootstrap to follow the current
docker install instructions.
Removing centos as it's a discontinued distribution.
Adding a check to ensure integration tests are skipped unless they
are run by a branch (a public fork does not pass required
integration test credentials).
bigtableadmin was not enabled in the bootstrapping script.
Also running the bootstrap script on every CI run, to ensure
the test environment is properly set up.
Compute_url_map was broken by #509: It also merged in #393, which
has an erroneous understanding that compute_url_map always returns
a diff (integration tests show it does not).
Adding a cleanup script to help with environment hygiene.
Added cleanup to CI to help make tests less flakey.
To help catch issues from PRs that would regress behavior,
adding a GitHub action similar to unit tests to run integration
tests.
GitHub actions do not pass secrets to actions which are triggered
by PRs sent from forks. As a result, it is not possible to have CI
run on the forks from external contributors. Currently implementing a
process that requires manual review until a more direct solution is
found.
Adding some basic instructions for future maintainers and contributors.
