Giter Site home page Giter Site logo

makeomatic / ms-users Goto Github PK

View Code? Open in Web Editor NEW
8.0 8.0 14.0 6.28 MB

Service for handling user's management via amqp transport layer. Docs are available at

Home Page: https://makeomatic.github.io/ms-users/

License: MIT License

JavaScript 97.95% Shell 0.12% Lua 1.75% Dockerfile 0.10% Handlebars 0.08%
amqp microservice node distributed-systems user-management microfleet amqp-layer docker-image

ms-users's Introduction

Microservice for handling users over AMQP transport layer

npm version Build Status semantic-release Commitizen friendly codecov.io Code Climate

Installation

npm i ms-users -S

Overview

Starts horizontally scalable nodejs worker communicating over amqp layer with redis cluster backend. Supports a broad range of operations for working with users. Please refer to the configuration options for now, that contains description of routes and their capabilities. Aims to provide a complete extendable solution to user's management.

Configuration

TODO

Endpoint description

Currently available on github pages

Docker images

Built docker images are available: https://hub.docker.com/r/makeomatic/ms-users/

ms-users's People

Contributors

2b1q avatar afoninsky avatar aleksxor avatar annahassel avatar avaddonval avatar avvs avatar brrenat avatar dependabot[bot] avatar freele avatar fuwaneko avatar greenkeeperio-bot avatar jenyapoyarkov avatar o-cappasity avatar pajgo avatar sashabratchikov avatar semantic-release-bot avatar sky3d avatar watchdg avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

ms-users's Issues

An in-range update of ms-mailer-client is breaking the build 🚨

Version 6.0.2 of ms-mailer-client just got published.

Branch Build failing 🚨
Dependency ms-mailer-client
Current Version 6.0.1
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

ms-mailer-client is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ semaphoreci The build failed on Semaphore. Details

Commits

The new version differs by 3 commits.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

cache invalidation when removing invites

{"name":"mservice","hostname":"fad50e30651d","pid":1,"level":50,"err":{"message":"404","name":"Error","stack":"Error: 404\n    at redis.hgetall.then.then.data (/src/node_modules/ms-token/lib/backends/redis/redis.js:149:15)\n    at tryCatcher (/src/node_modules/bluebird/js/release/util.js:16:23)\n    at Promise._settlePromiseFromHandler (/src/node_modules/bluebird/js/release/promise.js:510:31)\n    at Promise._settlePromise (/src/node_modules/bluebird/js/release/promise.js:567:18)\n    at Promise._settlePromise0 (/src/node_modules/bluebird/js/release/promise.js:612:10)\n    at Promise._settlePromises (/src/node_modules/bluebird/js/release/promise.js:691:18)\n    at Async._drainQueue (/src/node_modules/bluebird/js/release/async.js:138:16)\n    at Async._drainQueues (/src/node_modules/bluebird/js/release/async.js:148:10)\n    at Immediate.Async.drainQueues (/src/node_modules/bluebird/js/release/async.js:17:14)\n    at runCallback (timers.js:574:20)\n    at tryOnImmediate (timers.js:554:5)\n    at processImmediate [as _immediateCallback] (timers.js:533:5)"},"msg":"404","time":"2016-09-14T21:19:52.563Z","v":0}

An in-range update of @microfleet/core is breaking the build 🚨

Version 8.0.2 of @microfleet/core just got published.

Branch Build failing 🚨
Dependency @microfleet/core
Current Version 8.0.1
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

@microfleet/core is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ semaphoreci The build failed on Semaphore. Details

Release Notes v8.0.2

<a name"8.0.2">

8.0.2 (2017-06-09)

Bug Fixes

Breaking Changes

  • adds flow declarations, rewritten docs, rebranded to @microfleet, upgraded all deps to latest: socket.io 2.x.x, boom 5.x.x, ms-validation 5.x.x, ms-amqp-transport 9.x.x

Refactor:

  • added flow declarations

Docs:

  • added missing jsdoc descriptions
  • example of a simple action
  • added roadmap
  • updated references to new repo, add sponsorship data

Fixes:

  • socket.io monkey-patch to fix middleware issue
  • updated message generation in hapi.js adapter
  • amqp plugin default configuration
  • migrations current version check logic bug

(53ec133a)

Commits

The new version differs by 4 commits.

  • f4740d4 fix: redis migrations (#247)
  • 4efdeb4 chore: update badge
  • de2d377 chore: updated deps
  • 55b84a8 chore: change prepublish to prepublishOnly script as designed

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of lighthouse is breaking the build 🚨

Version 2.1.0 of lighthouse just got published.

Branch Build failing 🚨
Dependency lighthouse
Current Version 2.0.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As lighthouse is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ semaphoreci The build failed on Semaphore. Details

Commits

The new version differs by 72 commits ahead by 72, behind by 2.

  • 929602d v2.1.0
  • 6456464 bump extension to 2.1.0
  • d5f5c52 fix: normalize all times to navStart, remove traceviewer model (#2347)
  • 63b4ac1 Merge pull request #2444 from GoogleChrome/licenseheaders-mini
  • 0f03c47 Compact the license header (assorted core files)
  • 332ab0c Compact the license header (plots)
  • 1feb25e Compact the license header (report, report tests)
  • 1d01ab0 Compact the license header (gatherer tests)
  • 8af980b Compact the license header (audit tests)
  • 4747964 Compact the license header (core/lib)
  • d732741 Compact the license header (extension, viewer)
  • d3f68c5 Compact the license header (gather, driver, computed)
  • 64292ab Compact the license header (audits)
  • ef7f0ec Compact the license header (chrome-launcher & cli)
  • 8275b6e de-jsonify default.js (#2445)

There are 72 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of semantic-release is breaking the build 🚨

Version 6.3.6 of semantic-release just got published.

Branch Build failing 🚨
Dependency semantic-release
Current Version 6.3.5
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As semantic-release is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ semaphoreci The build failed on Semaphore. Details

Release Notes v6.3.6

<a name"6.3.6">

6.3.6 (2017-01-13)

Bug Fixes

  • package:
    • update github to version 8.0.0 (afd6ab75)
    • update nopt to version 4.0.0 (b10c8910)
Commits

The new version differs by 8 commits0.

  • af90de9 Merge pull request #355 from semantic-release/dep-updates
  • aa012b3 Merge branch 'greenkeeper/tap-9.0.0' into dep-updates
  • 5724b19 Merge branch 'greenkeeper/github-8.0.0' into dep-updates
  • 97a8e73 Merge branch 'caribou' into greenkeeper/nopt-4.0.0
  • 51e12a3 docs(package): fix 'home' link
  • afd6ab7 fix(package): update github to version 8.0.0
  • f80e056 chore(package): update tap to version 9.0.0
  • b10c891 fix(package): update nopt to version 4.0.0

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of eslint-plugin-import is breaking the build 🚨

Version 2.4.0 of eslint-plugin-import just got published.

Branch Build failing 🚨
Dependency eslint-plugin-import
Current Version 2.3.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As eslint-plugin-import is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ semaphoreci The build failed on Semaphore. Details

Commits

The new version differs by 10 commits.

  • 44ca158 update utils changelog
  • a3728d7 bump eslint-module-utils to v2.1.0
  • 3e29169 bump v2.4.0
  • ea9c92c Merge pull request #737 from kevin940726/master
  • 8f9b403 fix typos, enforce type of array of strings in allow option
  • 95315e0 update CHANGELOG.md
  • 28e1623 eslint-module-utils: filePath in parserOptions (#840)
  • 2f690b4 update CI to build on Node 6+7 (#846)
  • 7d41745 write doc, add two more tests
  • dedfb11 add allow glob for rule no-unassigned-import, fix #671

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of sinon is breaking the build 🚨

Version 2.3.3 of sinon just got published.

Branch Build failing 🚨
Dependency sinon
Current Version 2.3.2
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As sinon is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ semaphoreci The build failed on Semaphore. Details

Release Notes Make stubbing of static function properties possible
  • Fix #1450, make stubbing of static function properties possible
Commits

The new version differs by 24 commits.

  • bade318 Update docs/changelog.md and set new release id in docs/_config.yml
  • 65d4e88 Add release documentation for v2.3.3
  • 2204e72 2.3.3
  • 64034ee Update Changelog.txt and AUTHORS for new release
  • 1ece07c Merge pull request #1450 from raulmatei/fix-1445-sandbox-stubbing-static-function-property-throws-error
  • 452981c Fix 1445: make stubbing of static function properties possible
  • 25f3eeb Update sandbox configuration docs. (#1443)
  • c76fa2e Merge pull request #1444 from piperchester/patch-1
  • 6539d94 Update README.md
  • c6d01d8 Add missing function name (#1440)
  • 5f989a8 Remove confusing .withArgs from spy documentation (#1438)
  • 9ca272e Remove superfluous calls in example (#1437)
  • 9e3eac3 Merge pull request #1436 from sinonjs/feature-detect-name-property
  • 65d3d7b Feature detect function name property in issue 950
  • e0c75bd Add test for #950, show that it has been fixed (#1435)

There are 24 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of chrome-remote-interface is breaking the build 🚨

Version 0.23.2 of chrome-remote-interface just got published.

Branch Build failing 🚨
Dependency chrome-remote-interface
Current Version 0.23.1
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As chrome-remote-interface is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ semaphoreci The build failed on Semaphore. Details

Commits

The new version differs by 8 commits.

  • 31e7248 Bump version
  • 0a14959 Remove the headless issues note in the README
  • 5db186b Fix README space
  • b84ba58 Fetch the protocol from Chrome itself when possible
  • c0a6b4d Allow to run the linter without Chrome running
  • ef97bd3 Travis CI: make curl completely silent
  • 5f061ca Use Chrome headless
  • bbf642a Travis CI: remove sudo requirement

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this πŸ’ͺ.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.


Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.


Good luck with your project ✨

Your semantic-release bot πŸ“¦πŸš€

An in-range update of redis-filtered-sort is breaking the build 🚨

Version 2.1.2 of redis-filtered-sort just got published.

Branch Build failing 🚨
Dependency redis-filtered-sort
Current Version 2.1.1
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

redis-filtered-sort is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ semaphoreci The build failed on Semaphore. Details

Commits

The new version differs by 2 commits0.

  • bd03910 2.1.2
  • d869cb6 fix: a few return conditions where we need to return key

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of @makeomatic/deploy is breaking the build 🚨

Version 1.7.17 of @makeomatic/deploy just got published.

Branch Build failing 🚨
Dependency @makeomatic/deploy
Current Version 1.7.16
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As @makeomatic/deploy is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ semaphoreci The build failed on Semaphore. Details

Commits

The new version differs by 2 commits.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

Documentation on how to run.

I think it would be nice if there was documentation on how to run the project. It would help those evaluating the project.

An in-range update of @makeomatic/deploy is breaking the build 🚨

Version 1.9.2 of @makeomatic/deploy just got published.

Branch Build failing 🚨
Dependency @makeomatic/deploy
Current Version 1.9.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As @makeomatic/deploy is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ semaphoreci The build failed on Semaphore. Details

Commits

The new version differs by 2 commits.

  • 8da71c8 1.9.2
  • 8f980b6 fix: report response body in captureResponseBody errors

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of @microfleet/core is breaking the build 🚨

Version 8.1.0 of @microfleet/core just got published.

Branch Build failing 🚨
Dependency @microfleet/core
Current Version 8.0.4
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

@microfleet/core is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ semaphoreci The build failed on Semaphore. Details

Release Notes v8.1.0

<a name"8.1.0">

8.1.0 (2017-06-11)

Features

Commits

The new version differs by 1 commits.

  • 7cb39c5 feat: add action.passAuthError

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of common-errors is breaking the build 🚨

Version 1.0.1 of common-errors just got published.

Branch Build failing 🚨
Dependency common-errors
Current Version 1.0.0
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

common-errors is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ semaphoreci The build failed on Semaphore. Details

Commits

The new version differs by 5 commits ahead by 5, behind by 1.

  • 03412bc version 1!
  • a54edc8 Merge pull request #26 from shutterstock/npm5-compatible
  • 5d6e912 Make common-errors installable via npm5
  • 1c463c3 Merge pull request #25 from markstos/fix-readme-markdown
  • 688c381 Docs: Fix Markdown rendering of h3 tags and named anchors.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of jsonwebtoken is breaking the build 🚨

Version 7.4.1 of jsonwebtoken just got published.

Branch Build failing 🚨
Dependency jsonwebtoken
Current Version 7.4.0
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

jsonwebtoken is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ semaphoreci The build failed on Semaphore. Details

Commits

The new version differs by 4 commits.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of codecov is breaking the build 🚨

Version 2.2.0 of codecov just got published.

Branch Build failing 🚨
Dependency codecov
Current Version 2.1.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As codecov is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ semaphoreci The build failed on Semaphore. Details

Release Notes v2.2.0

Added: Support for Jenkins Blue Ocean
Added: Clear function to remove all discovered reports after uploading
Fix for Gitlab CI

Commits

The new version differs by 8 commits0.

  • 7f8a29b v2.2.0
  • 576b9fe add CI_REPOSITORY_URL to gitlab detection, fix #60
  • 74a44f2 added -C to unlink reports after uploading
  • d1bf5e4 Merge pull request #56 from rochdev/blue-ocean
  • 0a3cea3 Add support for Jenkins Blue Ocean
  • b365cd8 Merge pull request #57 from codecov/fix/cleanup
  • 7f220cc Removing old execSync code from tests
  • 4ba4609 v2.1.0

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

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.