Skip to content

Bump lewagon/wait-on-check-action from 1.2.0 to 1.3.1 #42

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Feb 16, 2023

Bumps lewagon/wait-on-check-action from 1.2.0 to 1.3.1.

Release notes

Sourced from lewagon/wait-on-check-action's releases.

v1.3.1

What's Changed

New Contributors

Full Changelog: lewagon/wait-on-check-action@v1.3.0...v1.3.1

v1.3.0

Update actions dependencies

Commits
  • e106e5c Update Readme
  • f602596 Merge pull request #72 from erikerikson/reusable-workflow-docs
  • f608cd6 Merge branch 'master' into reusable-workflow-docs
  • c7af1cc Merge pull request #77 from guidoiaquinti/patch-1
  • 58ae29f Shorter busywork
  • cdfa600 standardrb without any external action
  • 53bd766 Re-trigger master GHA workflows
  • 60446b9 Bump standardrb action version
  • 325e668 Add faraday-retry gem + standardrb --fix
  • b1319f7 Merge pull request #81 from hsbt/suppress-warnings
  • Additional commits viewable in compare view

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)

MarcialRosales and others added 2 commits January 30, 2023 20:51
With protocol plugins such as mqtt, or stomp, when
they accept an incoming connection, immediately after,
an internal amqp connection is created and the credentials received
during the initial connection are passed to the internal amqp
connection.

With AMQP 1.0 plugin things are different. It only creates
an internal amqp connection when a session is created.
However, the full credentials, i.e. username and password are
received during the initial connection establishment phase.
During that phase the user is authenticated and its username is
kept in User record.
However, when a session is established and the plugin has to create
an internal amqp connection, given that we are using Oauth2 backend,
we still need to pass around the token as password. However, at this
point we no longer have it.

Therefore, to have to preserve the password. This PR suggests to
optionally keep the token in the password attribute of the #user record
and #auth-user record for auth backend which are token based such as
oauth2. Other backend such as internal, http or ldap, do not need to
preseve the initial password because to authenticate the internal
amqp connection, they support "password-less" authentication, i.e. they
only check the user exists.
Bumps [lewagon/wait-on-check-action](https://github.com/lewagon/wait-on-check-action) from 1.2.0 to 1.3.1.
- [Release notes](https://github.com/lewagon/wait-on-check-action/releases)
- [Commits](lewagon/wait-on-check-action@v1.2.0...v1.3.1)

---
updated-dependencies:
- dependency-name: lewagon/wait-on-check-action
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Feb 16, 2023
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.

1 participant