Skip to content

Conversation

@abhishekkumams
Copy link
Contributor

@abhishekkumams abhishekkumams commented May 18, 2023

Why make this change?

What is this change?

  • cherry-picking fix for bugs found in 0.7

abhishekkumams and others added 2 commits May 18, 2023 11:36
## Why make this change?

- To update the files to use the correct reference of schema file.

## What is this change?

- removing usage of Azure storage links.
- updating it to be consistent with the other test files.

---------

Co-authored-by: Shyam Sundar J  <[email protected]>
## What is the issue?
- This issue occurs specifically when the environment variable is set
and `environmentBasedConfigFile` is not present and the user tries to do
`dab start`. It will search for the merged file and fail directly if the
merged file is not present. Ideally it should not and rather look for
the default file.
- Even though the merging was not happening and the method
`TryMergeConfigsIfAvailable` was returning false, the out file was not
empty and it was containing the name of expected mergeConfigFile.
 
## Why make this change?
- the merge config file name is generated and set as the config to be
used even if the merged config file is not available.
- This will make sure merge config file name is not used if it is not
available

## What is this change?

- Moving the line which creates the merged file name inside the
validation check for existence of the base and environment config.

## How was this tested?

- [x] Unit Tests
Copy link
Collaborator

@Aniruddh25 Aniruddh25 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks for the quick port!

@abhishekkumams abhishekkumams merged commit 2bd0a13 into release/0.7 May 19, 2023
@abhishekkumams abhishekkumams deleted the hot-fix-merge-config branch May 19, 2023 03:13
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.

4 participants