Skip to content
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

Test PR. Don't merge #3372

Conversation

gavindidrichsen
Copy link
Contributor

@gavindidrichsen gavindidrichsen commented Jan 15, 2025

No description provided.

Github actions do not currently verify whether bolt's module dependencies are valid.  In other worlds, bolt uses a number of puppet modules and these can be out-of-date or even missing dependencies.  This commit adds an extra step to CI that checks for missing dependecies.

Signed-off-by: Gavin Didrichsen <[email protected]>
Bolt is moving from opensource to private.  One contraint is that users must have a forge token.  A simple way to enforce this is to ensure an environment variable is present containing a valid forge token.  Environment variables are recognized as a sensible and secure method for passing credentials into applications due to their simplicity, security, and flexibility.  Therefore, I decided to pass forge token authentication via the `BOLT_FORGE_TOKEN` environment variable.

Signed-off-by: Gavin Didrichsen <[email protected]>
Signed-off-by: Gavin Didrichsen <[email protected]>
Prior to this commit all bolt tests had to be run in order to check a small change.  This commit allow individual tests to be re-run to shorten the dev iteration cycle.

Signed-off-by: Gavin Didrichsen <[email protected]>
@gavindidrichsen gavindidrichsen changed the title Inject an authentication token environment variable Test PR. Don't merge Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant