Thomas E Lackey 6e61aafd6e Add --fqdn-policy option to deploy-webapp-from-registry. (#802) ... 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: #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>		2024-05-03 19:24:42 +00:00
..
__init__.py	Webapp deploy (#662)	2023-11-27 22:02:16 -07:00
deploy_webapp_from_registry.py	Add --fqdn-policy option to deploy-webapp-from-registry. (#802)	2024-05-03 19:24:42 +00:00
deploy_webapp.py	Fix default webapp port number. (#740)	2024-02-09 01:20:41 +00:00
run_webapp.py	Support other webapp types (react, static). (#721)	2024-02-02 18:04:06 -06:00
undeploy_webapp_from_registry.py	Add support for annotations and labels in spec. (#739)	2024-02-09 00:11:07 +00:00
util.py	revert 5308ab1e4e (#788)	2024-05-03 19:24:42 +00:00