-
Notifications
You must be signed in to change notification settings - Fork 55
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
CLI-27: basic integration tests. #122
Conversation
the repo accidentally.
4207599
to
8da4efe
Compare
8da4efe
to
9db1711
Compare
There are no github action changes included in this PR. I'm working through understanding how we can set this up safely. |
@@ -0,0 +1,206 @@ | |||
// auth0-cli-config-generator: A command that generates a valid config file that can be used with auth0-cli. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for these small doc touches. Makes it feel 👌
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
General question on placement: should we put this in ./cmd/
instead? If not, curious to hear your thought process.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's only real use is to generate a config for integration testing by a CI pipeline (or a noop if a valid config exists already) so storing it outside of where it could add cognitive overhead for contributors not working on tooling for integration tests was the idea. I also wanted to ensure it didnt depend on any code within ./internal/
to keep it siloed and independent. Happy to move it to ./cmd/
and though -- just let me know.
type config struct { | ||
DefaultTenant string `json:"default_tenant"` | ||
Tenants map[string]tenant `json:"tenants"` | ||
} | ||
|
||
type tenant struct { | ||
Name string `json:"name"` | ||
Domain string `json:"domain"` | ||
AccessToken string `json:"access_token,omitempty"` | ||
ExpiresAt time.Time `json:"expires_at"` | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note for the future: we can probably consider re-using some of the same entities we have in the CLI since they resemble each other.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I made a comment on keeping it siloed but also happy to re-use entities in the CLI. I didn't want to add the coupling.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just some general questions on placement, but not a real blocker. 👍
…into cli-27-basic-integration-tests
Description
Initial attempt at basic integration tests.
References
Testing
Checklist
master