-
Notifications
You must be signed in to change notification settings - Fork 55
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'main' into spike-homebrew
- Loading branch information
Showing
833 changed files
with
127,339 additions
and
14,684 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| vendor/* linguist-generated=true |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -14,10 +14,10 @@ jobs: | |
| - name: Unshallow | ||
| run: git fetch --prune --unshallow | ||
|
|
||
| - name: Set up Go 1.15 | ||
| - name: Set up Go 1.16 | ||
| uses: actions/setup-go@v1 | ||
| with: | ||
| go-version: 1.15 | ||
| go-version: 1.16 | ||
|
|
||
| - name: Run GoReleaser | ||
| uses: goreleaser/[email protected] | ||
|
|
||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,51 @@ | ||
| # Contributor Code of Conduct | ||
|
|
||
| Our [company values](https://auth0.com/careers/culture) guide us in our day-to-day interactions and decision-making. Our open source projects are no exception. Trust, respect, collaboration and transparency are core values we believe should live and breathe within our projects. Our community welcomes participants from around the world with different experiences, unique perspectives, and great ideas to share. | ||
|
|
||
| ## Our Pledge | ||
|
|
||
| In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation. | ||
|
|
||
| ## Our Standards | ||
|
|
||
| Examples of behavior that contributes to creating a positive environment include: | ||
|
|
||
| - Using welcoming and inclusive language | ||
| - Being respectful of differing viewpoints and experiences | ||
| - Gracefully accepting constructive criticism | ||
| - Attempting collaboration before conflict | ||
| - Focusing on what is best for the community | ||
| - Showing empathy towards other community members | ||
|
|
||
| Examples of unacceptable behavior by participants include: | ||
|
|
||
| - Violence, threats of violence, or inciting others to commit self-harm | ||
| - The use of sexualized language or imagery and unwelcome sexual attention or advances | ||
| - Trolling, intentionally spreading misinformation, insulting/derogatory comments, and personal or political attacks | ||
| - Public or private harassment | ||
| - Publishing others' private information, such as a physical or electronic address, without explicit permission | ||
| - Abuse of the reporting process to intentionally harass or exclude others | ||
| - Advocating for, or encouraging, any of the above behavior | ||
| - Other conduct which could reasonably be considered inappropriate in a professional setting | ||
|
|
||
| ## Our Responsibilities | ||
|
|
||
| Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. | ||
|
|
||
| Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. | ||
|
|
||
| ## Scope | ||
|
|
||
| This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. | ||
|
|
||
| ## Enforcement | ||
|
|
||
| Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting us anonymously through [this form](https://goo.gl/forms/chVYUnA4bP70WGsL2). All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. | ||
|
|
||
| Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. | ||
|
|
||
| If you are unsure whether an incident is a violation, or whether the space where the incident took place is covered by our Code of Conduct, **we encourage you to still report it**. We would prefer to have a few extra reports where we decide to take no action, than to leave an incident go unnoticed and unresolved that may result in an individual or group to feel like they can no longer participate in the community. Reports deemed as not a violation will also allow us to improve our Code of Conduct and processes surrounding it. If you witness a dangerous situation or someone in distress, we encourage you to report even if you are only an observer. | ||
|
|
||
| ## Attribution | ||
|
|
||
| This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,58 @@ | ||
| # Contributing to Auth0 projects | ||
|
|
||
| A big welcome and thank you for considering contributing to Auth0 open source projects! It’s people like you that make it a reality for users in our community. | ||
|
|
||
| Reading and following these guidelines will help us make the contribution process easy and effective for everyone involved. It also communicates that you agree to respect the time of the developers managing and developing these open source projects. In return, we will reciprocate that respect by addressing your issue, assessing changes, and helping you finalize your pull requests. | ||
|
|
||
| ## Quicklinks | ||
|
|
||
| * [Code of Conduct](#code-of-conduct) | ||
| * [Getting Started](#getting-started) | ||
| * [Issues](#issues) | ||
| * [Pull Requests](#pull-requests) | ||
| * [Getting Help](#getting-help) | ||
|
|
||
| ## Code of Conduct | ||
|
|
||
| We take our open source community seriously and hold ourselves and other contributors to high standards of communication. By participating and contributing to this project, you agree to uphold our [Code of Conduct](https://github.com/auth0/open-source-template/blob/master/CODE-OF-CONDUCT.md). | ||
|
|
||
| ## Getting Started | ||
|
|
||
| Contributions are made to this repo via Issues and Pull Requests (PRs). A few general guidelines that cover both: | ||
|
|
||
| - To report security vulnerabilities, please use our [Responsible Disclosure Program](https://auth0.com/whitehat) which is monitored by our security team. | ||
| - Search for existing Issues and PRs before creating your own. | ||
| - We work hard to makes sure issues are handled in a timely manner but, depending on the impact, it could take a while to investigate the root cause. A friendly ping in the comment thread to the submitter or a contributor can help draw attention if your issue is blocking. | ||
| - If you've never contributed before, see [the first timer's guide on our blog](https://auth0.com/blog/a-first-timers-guide-to-an-open-source-project/) for resources and tips on how to get started. | ||
|
|
||
| ### Issues | ||
|
|
||
| Issues should be used to report problems with the library, request a new feature, or to discuss potential changes before a PR is created. When you create a new Issue, a template will be loaded that will guide you through collecting and providing the information we need to investigate. | ||
|
|
||
| If you find an Issue that addresses the problem you're having, please add your own reproduction information to the existing issue rather than creating a new one. Adding a [reaction](https://github.blog/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) can also help be indicating to our maintainers that a particular problem is affecting more than just the reporter. | ||
|
|
||
| ### Pull Requests | ||
|
|
||
| PRs to our libraries are always welcome and can be a quick way to get your fix or improvement slated for the next release. In general, PRs should: | ||
|
|
||
| - Only fix/add the functionality in question **OR** address wide-spread whitespace/style issues, not both. | ||
| - Add unit or integration tests for fixed or changed functionality (if a test suite already exists). | ||
| - Address a single concern in the least number of changed lines as possible. | ||
| - Include documentation in the repo or on our [docs site](https://auth0.com/docs). | ||
| - Be accompanied by a complete Pull Request template (loaded automatically when a PR is created). | ||
|
|
||
| For changes that address core functionality or would require breaking changes (e.g. a major release), it's best to open an Issue to discuss your proposal first. This is not required but can save time creating and reviewing changes. | ||
|
|
||
| In general, we follow the ["fork-and-pull" Git workflow](https://github.com/susam/gitpr) | ||
|
|
||
| 1. Fork the repository to your own Github account | ||
| 2. Clone the project to your machine | ||
| 3. Create a branch locally with a succinct but descriptive name | ||
| 4. Commit changes to the branch | ||
| 5. Following any formatting and testing guidelines specific to this repo | ||
| 6. Push changes to your fork | ||
| 7. Open a PR in our repository and follow the PR template so that we can efficiently review the changes. | ||
|
|
||
| ## Getting Help | ||
|
|
||
| Join us in the [Auth0 Community](https://community.auth0.com) and post your question there in the correct category with a descriptive tag. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,21 @@ | ||
| The MIT License (MIT) | ||
|
|
||
| Copyright (c) 2021 Auth0, Inc. <[email protected]> (http://auth0.com) | ||
|
|
||
| Permission is hereby granted, free of charge, to any person obtaining a copy | ||
| of this software and associated documentation files (the "Software"), to deal | ||
| in the Software without restriction, including without limitation the rights | ||
| to use, copy, modify, merge, publish, distribute, sublicense, and/or sell | ||
| copies of the Software, and to permit persons to whom the Software is | ||
| furnished to do so, subject to the following conditions: | ||
|
|
||
| The above copyright notice and this permission notice shall be included in all | ||
| copies or substantial portions of the Software. | ||
|
|
||
| THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR | ||
| IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, | ||
| FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE | ||
| AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER | ||
| LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, | ||
| OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE | ||
| SOFTWARE. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,7 +1,9 @@ | ||
| # Auth0 CLI | ||
| # Auth0 CLI (Experimental) | ||
|
|
||
| `auth0` is the command line to supercharge your development workflow. | ||
|
|
||
| > Note: This CLI is currently in an experimental state and is not supported by Auth0. It has not had a complete security review, and we do not recommend using it to interact with production tenants. | ||
| Build, test, and manage your integration with **[Auth0](http://auth0.com/)** directly from your **terminal**. | ||
|
|
||
|  | ||
|
|
@@ -20,11 +22,129 @@ Build, test, and manage your integration with **[Auth0](http://auth0.com/)** dir | |
|
|
||
| > see more completion options: `auth0 completion -h` | ||
| ## Usage | ||
|
|
||
| After installation, you should have the `auth0` command available: | ||
|
|
||
| ```bash | ||
| auth0 [command] | ||
|
|
||
| # For any help, run --help after a specific command, e.g.: | ||
| auth0 [command] --help | ||
| ``` | ||
|
|
||
| ### Onboarding Journey | ||
|
|
||
| Following these instructions will give you a sense of what's possible with the | ||
| auth0 CLI. To start, you will have to login: | ||
|
|
||
| #### Login | ||
|
|
||
| ```bash | ||
| auth0 login | ||
| ``` | ||
|
|
||
| #### Creating your application | ||
|
|
||
| If you haven't created an application yet, you may do so by running the | ||
| following command: | ||
|
|
||
| ```bash | ||
| auth0 apps create | ||
| ``` | ||
|
|
||
| A screen similar to the following will be presented after successful app creation: | ||
|
|
||
| ```bash | ||
| $ auth0 apps create | ||
| Name: my awesome app | ||
| Type: Regular Web Application | ||
| Description: dev tester | ||
| Creating application... done | ||
|
|
||
| === travel0 application created | ||
|
|
||
| NAME my awesome app | ||
| TYPE regular web application | ||
| CLIENT ID vXAtoaFdhlmtWjpIrjb9AUnrGEAOH2MM | ||
| CLIENT SECRET QXV0aDAgaXMgaGlyaW5nISBhdXRoMC5jb20vY2FyZWVycyAK | ||
|
|
||
| ▸ Quickstarts: https://auth0.com/docs/quickstart/webapp | ||
| ▸ Hint: You might wanna try `auth0 test login --client-id vXAtoaFdhlmtWjpIrjb9AUnrGEAOH2MM` | ||
| ``` | ||
|
|
||
| As you might observe, the next thing to do would likely be to try logging in | ||
| using the client ID. | ||
|
|
||
| #### Testing the login flow | ||
|
|
||
| Whether or not you've created the application using the CLI or the management | ||
| dashboard, you'll be able to test logging in using a specific application. | ||
|
|
||
| If you have the client ID, you may specify it via the `--client-id` flag, | ||
| otherwise a prompt will be presented: | ||
|
|
||
| ``` | ||
| auth0 test login | ||
| ``` | ||
|
|
||
| #### Tailing your logs | ||
|
|
||
| Once you have a few logins in place, you might wanna tail your logs. This is | ||
| done by running the following command: | ||
|
|
||
| ```bash | ||
| auth0 logs -f | ||
| ``` | ||
|
|
||
| After running that, one might see the following output: | ||
|
|
||
| ``` | ||
| Success Login 9 minutes ago Username-Password-Authentic... my awesome app | ||
| ``` | ||
|
|
||
| If there are errors encountered, such as the following example, you may run it | ||
| with the `--debug` flag as follows: | ||
|
|
||
| ```bash | ||
| auth0 logs -f --debug | ||
| ``` | ||
|
|
||
| The full raw data will be displayed below every error: | ||
|
|
||
| ``` | ||
| Failed Login hello 7 minutes ago N/A my awesome app | ||
| id: "90020210306002808976000921438552554184272624146777636962" | ||
| logid: "90020210306002808976000921438552554184272624146777636962" | ||
| date: 2021-03-06T00:28:04.91Z | ||
| type: f | ||
| clientid: vXAtoaFdhlmtWjpIrjb9AUnrGEAOH2MM | ||
| clientname: my awesome app | ||
| ip: 1.2.3.4 | ||
| description: hello | ||
| locationinfo: {} | ||
| details: | ||
| body: | ||
| action: default | ||
| password: '*****' | ||
| state: QXV0aDAgaXMgaGlyaW5nISBhdXRoMC5jb20vY2FyZWVycyAK | ||
| username: [email protected] | ||
| connection: Username-Password-Authentication | ||
| error: | ||
| message: hello | ||
| oauthError: access_denied | ||
| type: oauth-authorization | ||
| qs: {} | ||
| session_id: QXV0aDAgaXMgaGlyaW5nISBhdXRoMC5jb20vY2FyZWVycyAK | ||
| userid: auth0|QXV0aDAgaXMgaGlyaW5nISBhdXRoMC5jb20vY2FyZWVycyAK | ||
| ``` | ||
|
|
||
| ## Contributing | ||
|
|
||
| Please check the [contributing guidelines](CONTRIBUTING.md). | ||
|
|
||
|
|
||
| ## Author | ||
| ## Author | ||
|
|
||
| [Auth0](https://auth0.com) | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.