kapicorp / kapitan

Generic templated configuration management for Kubernetes, Terraform and other things
https://kapitan.dev
Apache License 2.0
1.8k stars 197 forks source link

Accept ".yaml" files as targets #756

Open dive-deeper opened 3 years ago

dive-deeper commented 3 years ago

Describe the bug/feature Kapitan should accept .yaml files as input (targets), similar to how it can produce them.

To Reproduce Steps to reproduce the behavior:

  1. Create a sample repository with targets as .yaml files
  2. Execute kapitan compile
  3. See Error: no targets found
  4. Change the target to .yml and see it work

Expected behavior Kapitan compiles independently of input format (yml vs yaml)

If it's a bug (please complete the following information):

Thanks

bdnf commented 2 years ago

In addition to this, if one of the files referenced in targets has an extension .yaml, the compile call is failing with a cryptic error, i.e.:

kapitan compile -t microservice

Inventory reclass error: -> 
   Inventory Queries:
   -> microservice
      In yaml_fs:///workspace/kapitan/inventory/targets/microservice.yml
      Class base not found under yaml_fs://./inventory/classes
ademariag commented 2 years ago

Thank you @bdnf, this has to do with the kapitan/reclass component. I will transfer the issue.

galactus009 commented 2 years ago

any update on issue ? what is proper behaviour. should be using .yml/.yaml or both can be used

github-actions[bot] commented 3 weeks ago

This issue is stale because it has been open for 1 year with no activity. Remove the stale label or comment if this issue is still relevant for you. If not, please close it yourself.