This repository was archived by the owner on Aug 10, 2020. It is now read-only.
Open
Conversation
This allows users to specify multiple gossfiles to run for validate and serve. This was added because the default behavior of merging gossfiles by overwriting keys isn't always desirable. Deep merging gossfiles is not an option, as there are users (goss-org#150) who rely on the overwriting behavior.
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Add a new global flag
--additional-gossfilesto specify additional gossfiles to run in addition to what is specified by-g.Only works with
serveandvalidate. This is because we avoid merging the gossfiles together entirely and can't produce a single YAML/JSON file with all the tests.This is motivated by wanting to run multiple gossfiles that have conflicting keys in them. Since the keys used are file paths/users/services/etc, it isn't possible to specify different tests in different gossfiles for a single resource due to the behaviour of
mergeGoss.Modifying
mergeGossto perform deep merges is not an option, as there are users (goss-org#150) who rely on the overwriting behaviour to mask tests.