Summary

Deployments can be paused and resumed (spec.paused). We could create a lua action for Deployments to modify this field.

Motivation

An action that allows this would remove the kubectl access currently needed for doing this.

Proposal

Implement the lua script for a pause and resume action for Deployments.

Is it possible to add a check if unleash variable is indeed a json, and disable the option of saving it unless it is?
For example, created a variable for a toggle and selected type to be a json, but I've inserted a string instead of a json and was able to save and pull the value.

{'name': 'test', 'payload': {'type': 'json', 'value': 'not a json'}, 'weightType': 'variable', 'enabled': True}

Hi,

It seems like naming a remote is subject to certain limitations as groupadd is executed (potentially 32chars?).

Example

apiVersion: gitkube.sh/v1alpha1
kind: Remote
metadata:
  name: app-remote
  namespace: my-really-really-really-long-ns

k logs po/gitkub

Environment

Liquibase Version:
4.1.0
Also latest master

Liquibase Integration & Version:
gradle, unknown version

Liquibase Extension(s) & Version:

Database Vendor & Version:
PostgreSQL: 12.X (occurs on all supported versions)

Operating System Type & Version:
MacOS 11.4 (20F71), but will occur on all supported OSs

Description

A clear and concis

https://github.com/google/starlark-go/blob/master/doc/spec.md

It should satisfy our reproducibility needs (like jsonnet) and could be easier to write agola config files.

Like in #137 we should provide build context information.