Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump ansible from 2.2.0.0 to 2.6.18 #25

Closed
wants to merge 2 commits into from

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Mar 28, 2020

Bumps ansible from 2.2.0.0 to 2.6.18.

Release notes

Sourced from ansible's releases.

v2.5.0 Beta 1

No release notes provided.

v2.5.0 Alpha 1

No release notes provided.

THESE ARE NOT OUR OFFICIAL RELEASES

For official tarballs go to https://releases.ansible.com

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

Lorenzo Zolfanelli and others added 2 commits March 28, 2020 18:47
Only one key is managed by Ansible at time, if not-managed keys are
present in user_ca.pub they are not removed, but the new key is
appended to the file.

If the ansible-managed key is changed it is overwritten.
The ansible-managed key is detected using a leadind tag in the key
line in user_ca.pub.

Maybe it would be best to have a "key" version parameter and variable
with options to enable key rotation/revocation.

Anyway it provides an easy way to push new user ca while machine already
configured with previous version of this role will still accept login
from user with certificate issued from the older cas.
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Mar 28, 2020
@zolfariot zolfariot mentioned this pull request Mar 30, 2020
@dependabot @github
Copy link
Author

dependabot bot commented on behalf of github Apr 7, 2021

Superseded by #30.

@dependabot dependabot bot closed this Apr 7, 2021
@dependabot dependabot bot deleted the dependabot/pip/ansible-2.6.18 branch April 7, 2021 23:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants