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

Regression fix for knack config file chaining functionality #577

Merged
merged 5 commits into from
May 6, 2019

Conversation

atbagga
Copy link
Collaborator

@atbagga atbagga commented May 6, 2019

Issue: Configuration read is failing and hence tests were failing since organization and project are set via config in tests

Reason: Breaking change: Knack has introduced the concept of scoped configurations which allows chaining of config files. For back compat they allow not using this feature.
The new setter function added in the same PR if used will handle setting the values such that they can be retrieved using the getter. PR link - microsoft/knack#148

Fix: Used the new knack setter function to be consistent in reading and writing the file using knack
CLIConfig class functions.

Fix 2:
Also making a change to not display the value of environment variables anymore in config list command. Since it might end up displaying secrets set in environment variables.

@atbagga atbagga changed the title Configure list should not show secrests Configure list should not show secrets on console May 6, 2019
@atbagga atbagga changed the title Configure list should not show secrets on console Configure list should not show Env Var Values on console May 6, 2019
@atbagga atbagga force-pushed the users/atbagga/configfix branch from f2fff77 to 92b8958 Compare May 6, 2019 08:20
@atbagga atbagga changed the title Configure list should not show Env Var Values on console Regression fix for knack config file chaining functionality May 6, 2019
@atbagga atbagga merged commit c2283e5 into master May 6, 2019
@atbagga atbagga deleted the users/atbagga/configfix branch May 6, 2019 17:21
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.

3 participants