Łukasz Oleś
Łukasz Oleś
## Description Sometimes we need to create so-called "Umbrella" manifests where we want to deploy several applications. This requires creating one Interface, InterfaceGroup, Types and so on. The unique part...
## Description Our Manifests generator for Terraform, generates Type with input data. It misses an information about required variables and default values. We should add this information so validator can...
## Description In case of the Redis chart, not all values from `values.yaml` are defined in `values.schema.json` - see https://github.com/bitnami/charts/tree/master/bitnami/redis ## Expected behavior It should be possible to validate all...
## Description When action fails, there is no way to fix it. It's already possible to run `argo retry` and workflow will continue. `capact action watch` will show the progress....
## Description Making Capact to work with the public clouds like AWS or GCP requires some manual steps to configure Type Instances with credentials. ~And we even have no docs...
## Description If we want to run Helm chart we need to create an Interface and Implementation for it. Sometimes we just want to run Chart in the workload and...
## Description Currently if one manifest is running another one. Using `capact-action` we have no way to set input-parameters for nested parameters. Using Action Policy we can overwrite or pass...
## Description `capact upgrade` and `capact install` share some code, but other code is duplicated. 1. See https://github.com/capactio/capact/pull/408#pullrequestreview-714754602 2. Usage of `InputParameters` should be rethought. For example, because of the...