v1.1.0-f1fdc48-202408282317

Work around this bug: https://github.com/python/cpython/pull/14064 (#…

v1.1.0-a54072d-202408281733

Add --config-ref flag. (#939)

Add a flag to re-use config.

Reviewed-on: https://git.vdb.to/cerc-io/stack-orchestrator/pulls/939
Co-authored-by: Thomas E Lackey <[email protected]>
Co-committed-by: Thomas E Lackey <[email protected]>

v1.1.0-fa21ff2-202408271955

Support uploaded config, add 'publish-webapp-deployer' and 'request-w…

v1.1.0-44b9709-202408201744

Use Laconic version of ping-pub (#930)

Reviewed-on: https://git.vdb.to/cerc-io/stack-orchestrator/pulls/930
Co-authored-by: David Boreham <[email protected]>
Co-committed-by: David Boreham <[email protected]>

v1.1.0-e56da7d-202408152033

Add support for k8s pod to node affinity and taint toleration (#917)

Reviewed-on: https://git.vdb.to/cerc-io/stack-orchestrator/pulls/917
Reviewed-by: Thomas E Lackey <[email protected]>
Co-authored-by: David Boreham <[email protected]>
Co-committed-by: David Boreham <[email protected]>

v1.1.0-8576137-202408140025

Convert port to string. (#919)

The str type check doesn't work if the port is a ruamel.yaml.scalarstring.SingleQuotedScalarString or ruamel.yaml.scalarstring.DoubleQuotedScalarString

Reviewed-on: https://git.vdb.to/cerc-io/stack-orchestrator/pulls/919
Co-authored-by: Thomas E Lackey <[email protected]>
Co-committed-by: Thomas E Lackey <[email protected]>

v1.1.0-5c275aa-202408141804

Defensively handle errors examining app requests. (#922)

Related to https://git.vdb.to/cerc-io/webapp-deployment-status-api/issues/10

There are two issues in that.  One is that the output probably changed recently, whether in the client or server, where no matching record is found by ID (Note this is specific to `laconic record get --id <v>` and does not seem to apply to the similar command to retrieve a record by name, `laconic name resolve <n>`).

Rather than returning `[]` it is now returning `[ null ]`.  This cause us to think there *was* an application record found, and we attempt to treat the `null` entry like an Application object.  That's fixed by filtering out null responses, which is a good precaution for the deployer, though I think it makes sense to ask whether this new behavior by the client/server is correct.  Seems suspicious.

The other issue is that all the defensive checks we had in place to deal with broken/bad AppDeploymentRequests were around the _build_.  This error was coming much earlier, merely when parsing and examining the request to see if it needed to be handled at all.

I have now added similar defensive error handling around that portion of the code.

Reviewed-on: https://git.vdb.to/cerc-io/stack-orchestrator/pulls/922
Reviewed-by: zramsay <[email protected]>
Co-authored-by: Thomas E Lackey <[email protected]>
Co-committed-by: Thomas E Lackey <[email protected]>

v1.1.0-65c1cdf-202408132047

Fix crash if port has int type in yaml (#918)

Reviewed-on: https://git.vdb.to/cerc-io/stack-orchestrator/pulls/918
Reviewed-by: Thomas E Lackey <[email protected]>
Co-authored-by: David Boreham <[email protected]>
Co-committed-by: David Boreham <[email protected]>

v1.1.0-265699b-202408131748

Allow to disable kind cluster management for testing (#915)

Reviewed-on: https://git.vdb.to/cerc-io/stack-orchestrator/pulls/915
Co-authored-by: David Boreham <[email protected]>
Co-committed-by: David Boreham <[email protected]>

v1.1.0-6087e1c-202408100232

Copy config under a volume for Docker (similar to a ConfigMap for K8S…