cesarbr / knot-cloud-sdk-js-authenticator Goto Github PK

What problem does this feature solve?

Currently, during the release phase, we have to manually:

• Update the library version
• Update the CHANGELOG
• Make a release commit
• Open a PR for this commit
• Wait for approval
• Update the package in NPM

This takes a lot of time, given that we have to repeat this for all our repos and that some packages depend on other ones to be released so that we can update their version on the project's package.json. As a consequence, sometimes we spend days on the release process, instead of using this time to improve testing, find bugs, and so on.

What does the proposed API look like?

As a solution, it was proposed by some members of the project that we create a continuous integration (CI) workflow that builds and tests Node.js code. If the CI tests pass, we may configure it to deploy the code or publish a package.

This may be achieved using GitHub Actions (there is even a guide for Node).

Other information:

As proposed by @ramonhpr, here, we could make use of concepts like using cache (to install npm packages just when the package.lock has changed), or using npm ci and OS platform build.

As an application developer, I want to be able to interact with the KNoT Cloud authenticator service programmatically so that I am able to manage and authenticate users from my applications and not only via KNoT Cloud UI.

• Bootstrap library project
• Add create user function
• Add forgot password function
• Add reset password function
• Add authenticate function