Previously with csv-merger we removed the Alm examples in the CSV. This is to save space as our bundles are quite large.
Now that we are using the raw data generated by operator-sdk's 'generate bundle' command the config/sample data is getting merged into the generated CSV for openstack-operator. As we had multiple controlplanes in the kustomization.yaml file this meant lots of extra YAML examples which aren't needed.
In order to maintain the previous behavior of effectively removing ALM examples, but still passing bundle generate validations this commit creates '_empty.yaml' versions of each CR and then uses those in the kustomization.yaml.
Needs approval from an approver in each of these files:
- ~~[OWNERS](https://github.com/openstack-k8s-operators/openstack-operator/blob/main/OWNERS)~~ [dprince,fao89]
Approvers can indicate their approval by writing `/approve` in a comment
Approvers can cancel approval by writing `/approve cancel` in a comment
Previously with csv-merger we removed the Alm examples in the CSV. This is to save space as our bundles are quite large.
Now that we are using the raw data generated by operator-sdk's 'generate bundle' command the config/sample data is getting merged into the generated CSV for openstack-operator. As we had multiple controlplanes in the kustomization.yaml file this meant lots of extra YAML examples which aren't needed.
In order to maintain the previous behavior of effectively removing ALM examples, but still passing bundle generate validations this commit creates '_empty.yaml' versions of each CR and then uses those in the kustomization.yaml.