You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 22, 2021. It is now read-only.
The kubecf templates contain complex logic that is currently only covered by smoke and acceptance tests.
There should be unit tests in the kubecf repo itself that verify that when the template generated ops files are applied to the deployment manifest, the results are what is expected.
Each test should be a YAML config file plus a ruby script, that reads the interpolated deployment manifest and verifies that expected structures exist and have the expected content (or don't exist, as the case may be).
The text was updated successfully, but these errors were encountered:
The kubecf templates contain complex logic that is currently only covered by smoke and acceptance tests.
There should be unit tests in the kubecf repo itself that verify that when the template generated ops files are applied to the deployment manifest, the results are what is expected.
This means we need to use
helm template
to render the YAML files, but then also apply the ops against the manifest. There is code in https://github.com/cloudfoundry-incubator/kubecf/blob/cf682c1/scripts/image_list.rb#L176-L191 that does this usingbosh interpolate
. This only works because we are not yet making use of theqcopy
andqmove
ops that have been added to the operator in cloudfoundry-incubator/quarks-operator#900.Ideally we would want to use
quarks-operator interpolate
, but until such a feature exist we can also use @mook-as's tool at https://github.com/mook-as/go-patch-cmd.Each test should be a YAML config file plus a ruby script, that reads the interpolated deployment manifest and verifies that expected structures exist and have the expected content (or don't exist, as the case may be).
The text was updated successfully, but these errors were encountered: