Repository navigation
fix: print the Business tier with its name in the startup log - #45
Merged
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
TIER_LABELSinsrc/client.jshad no entry forbusiness, so a bot on the Business tier printed the raw key on startup:API key valid → business. It printsBusinessnow. Seen on the MSK support bot after the 2.22.0 update. The colour falls back to the default green as before.No release with this one, it goes out with the next version.
Related Issue
None.
Type of Change
How Was This Tested?
npm test: 391 passed. One-line change to a console label.Checklist
client.t(...)(not applicable, console log label)MSK_API_KEYnpm start) and I verified my change on a test serverCHANGELOG.mdentry under[Unreleased]