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

Add omitempty tag to bundle git details #372

Merged
merged 1 commit into from
May 1, 2023
Merged

Conversation

shreyas-goenka
Copy link
Contributor

Changes

Add omit empty tag to git details. Otherwise this field becomes a required field in the config json schema

Tests

Tested by regenerating the json schema and checking that the git field is now optional

Copy link
Contributor

@mgyucht mgyucht left a comment

Choose a reason for hiding this comment

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

Change LGTM. I feel like this should be easily caught by a unit test for parsing bundle files. Does such a test exist? If not, could you add one please?

@shreyas-goenka
Copy link
Contributor Author

Good point. Created a ticket to track it: https://databricks.atlassian.net/browse/DECO-740. We do not have any such existing tests, we rely on the red hat yaml extension to do the validation for us. However validation should be possible using a library like https://github.com/santhosh-tekuri/jsonschema

@shreyas-goenka shreyas-goenka merged commit 37af3d5 into main May 1, 2023
@shreyas-goenka shreyas-goenka deleted the git-omitempty branch May 1, 2023 12:34
@shreyas-goenka shreyas-goenka mentioned this pull request May 15, 2023
shreyas-goenka added a commit that referenced this pull request May 15, 2023
## Changes
## 0.0.32
* Add support for variables in bundle config. Introduces 4 ways of
setting variable values, which in decreasing order of priority are:
([#383](#383)).
	1. Command line flag. For example: `--var="foo=bar"`
	2. Environment variable. eg: BUNDLE_VAR_foo=bar
	3. Default value as defined in the applicable environments block
	4. Default value defined in variable definition
* Make the git details bundle config block optional
([#372](#372)).
* Fix api post integration tests
([#371](#371)).
* Fix table of content by removing not required top-level item
([#366](#366)).
* Fix printing the tasks in job output in DAG execution order
([#377](#377)).
* Improved error message when 'bricks bundle run' is executed before
'bricks bundle deploy'
([#378](#378)).
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.

None yet

2 participants