fix: pass FeatureOS creds via env vars in daily workflow#5
Open
mzeier wants to merge 1 commit into
Open
Conversation
The daily report logged 'Error: API Key not set.' from featureos-cli, producing an empty FeatureOS section. The workflow hand-wrote ~/.featureos.yaml with keys 'api_key'/'jwt', but the CLI's config fields are APIKey/JWTToken, so those keys read as unset. Drop the file-writing step and pass the documented env vars (FEATUREOS_API_KEY / FEATUREOS_JWT) directly to the generate step, matching the weekly workflow which already does this correctly.
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
1 participant
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.
Problem
The daily report run logged:
so the report's FeatureOS / TB Pro Ideas section has been silently empty.
Root cause
The daily workflow hand-wrote
~/.featureos.yamlwith keysapi_key:/jwt:, but the@featureos/clibinary reads its credentials from config fieldsAPIKey/JWTToken(and env varsFEATUREOS_API_KEY/FEATUREOS_JWT). The underscore keys don't map, so the API key read as unset.Fix
Drop the file-writing step and pass the documented env vars directly to the generate step — exactly what the weekly workflow (
tbpro-weekly.yml) already does. Whitespace is stripped from the secrets the same way the weekly workflow strips them.Verified the env-var names against the CLI binary's own help output (
API Key (env: FEATUREOS_API_KEY),JWT Token (env: FEATUREOS_JWT)).