Thomas E Lackey
4126f2fc43
Webapp Test / Run webapp test suite (push) Failing after 5s
Details
Lint Checks / Run linter (push) Failing after 4s
Details
Deploy Test / Run deploy test suite (push) Failing after 3s
Details
Publish / Build and publish (push) Failing after 4s
Details
Smoke Test / Run basic test suite (push) Failing after 3s
Details
This add a new option `--fqdn-policy` to the `deploy-webapp-from-registry`. The default policy, `prohibit` means that `ApplicationDeploymentRequests` which specify a FQDN will be rejected. The `allow` policy will cause them to be processed. The `preexisting` policy will only process them if an existing `DnsRecord` exists in the registry with the correct ownership. The latter would be useful in conjunction with a pre-checking scheme in the UI (eg, that the DNS entry is properly configured, the domain is under the control of the requestor, etc.) Only after all the checks were successful would the `DnsRecord` be created, allowing for `ApplicationDeploymentRequests` to use it. Reviewed-on: https://git.vdb.to/cerc-io/stack-orchestrator/pulls/802 Reviewed-by: David Boreham <dboreham@noreply.git.vdb.to> Co-authored-by: Thomas E Lackey <telackey@bozemanpass.com> Co-committed-by: Thomas E Lackey <telackey@bozemanpass.com> |
||
|---|---|---|
| .. | ||
| compose | ||
| k8s | ||
| webapp | ||
| __init__.py | ||
| deploy.py | ||
| deploy_types.py | ||
| deploy_util.py | ||
| deployer.py | ||
| deployer_factory.py | ||
| deployment.py | ||
| deployment_context.py | ||
| deployment_create.py | ||
| images.py | ||
| spec.py | ||
| stack.py | ||
| stack_state.py | ||