1e0baf5f6c
* Add code generated using latest code-generator Signed-off-by: Sanket Sudake <sanketsudake@gmail.com> * Update client-go and respective dependencies to v0.19.2 Signed-off-by: Sanket Sudake <sanketsudake@gmail.com> * Upgrading CRD version Signed-off-by: Harsh Thakur <harshthakur9030@gmail.com> * Minor changes Signed-off-by: Harsh Thakur <harshthakur9030@gmail.com> * Resolved client-go calls as per new generated code Signed-off-by: Sanket Sudake <sanketsudake@gmail.com> * Function validations fix Signed-off-by: Harsh Thakur <harshthakur9030@gmail.com> * Fix environment and package validations Signed-off-by: Harsh Thakur <harshthakur9030@gmail.com> * Add basic validation to all CRDs Signed-off-by: Harsh Thakur <harshthakur9030@gmail.com> * Remove CRD installation related code Signed-off-by: Harsh Thakur <harshthakur9030@gmail.com> * Modify GHA for CRD installation Signed-off-by: Harsh Thakur <harshthakur9030@gmail.com> * Fix Package and HTTPTrigger validations Signed-off-by: Harsh Thakur <harshthakur9030@gmail.com> * Change Go version in CI to 1.15 Signed-off-by: Sanket Sudake <sanketsudake@gmail.com> * Style: kubebuilder marker change Signed-off-by: Harsh Thakur <harshthakur9030@gmail.com> * Fix test with deprecated fields Signed-off-by: Harsh Thakur <harshthakur9030@gmail.com> * Update kind node image to v1.16.15 in CI Signed-off-by: Sanket Sudake <sanketsudake@gmail.com> * Update kind node image to v1.19.11 in CI Signed-off-by: Sanket Sudake <sanketsudake@gmail.com> * Replace context Background with TODO for future implementation Signed-off-by: Sanket Sudake <sanketsudake@gmail.com> * Optimize initial CRD check code Signed-off-by: Sanket Sudake <sanketsudake@gmail.com> * Use Get call only to check CRDs Signed-off-by: Sanket Sudake <sanketsudake@gmail.com> * Add kustomize for CRD apply Signed-off-by: Sanket Sudake <sanketsudake@gmail.com> Co-authored-by: Sanket Sudake <sanketsudake@gmail.com>
Fission Specs ============= This is a set of specifications for a Fission app. This includes functions, environments, and triggers; we collectively call these things "resources". How to use these specs ---------------------- These specs are handled with the 'fission spec' command. See 'fission spec --help'. 'fission spec apply' will "apply" all resources specified in this directory to your cluster. That means it checks what resources exist on your cluster, what resources are specified in the specs directory, and reconciles the difference by creating, updating or deleting resources on the cluster. 'fission spec apply' will also package up your source code (or compiled binaries) and upload the archives to the cluster if needed. It uses 'ArchiveUploadSpec' resources in this directory to figure out which files to archive. You can use 'fission spec apply --watch' to watch for file changes and continuously keep the cluster updated. You can add YAMLs to this directory by writing them manually, but it's easier to generate them. Use 'fission function create --spec' to generate a function spec, 'fission environment create --spec' to generate an environment spec, and so on. You can edit any of the files in this directory, except 'fission-deployment-config.yaml', which contains a UID that you should never change. To apply your changes simply use 'fission spec apply'. fission-deployment-config.yaml ------------------------------ fission-deployment-config.yaml contains a UID. This UID is what fission uses to correlate resources on the cluster to resources in this directory. All resources created by 'fission spec apply' are annotated with this UID. Resources on the cluster that are _not_ annotated with this UID are never modified or deleted by fission.