microsoft / azure-schema-operator Goto Github PK

Extend tests and check updated status of the Eventhub SDK for go

The "Create Release" pipeline doesn't package the helm chart.
If the chart is not pre-packaged it will fail.

We need to trigger task package-helm and uploaded the generated package before releasing.
This is a simple fix as the task already exists.

The Azure-service-operator use kind http://kind.sigs.k8s.io/ to for local deployments.
the provide a simple way to install locally.

4 options:

• Use the same method they use (we can take the scripts/tasks as is)2.
• Minikube
• kube in Docker client
• We can also use k3s, which has lower resource footprint.

Review the installation guide

Describe the bug
When running the Dacpac on a specific target schema without specifying a template schema name in the configmap
cfgMap.Data["templateName"]

will result in an unhandled exception.
the manager will restart and the ClusterExecuter will remain stuck in Running state.

To Reproduce
Steps to reproduce the behavior:
Run the SQLServer flow on a target without specifying a templateName in the dacpac configMap.

Expected behavior
There are multiple issues and behaviors that need fixing here:

• WebHook validation on the input is expected as this is not a valid input.
• Error Event should be caught and handled
• ClusterExecuter should not remain in stuck state.

Test the Schema operator failure handling process.

We have 3 scenarios:

1. abort - stop reconcile on a broken state
2. ignore - stop reconcile on a successful state (ignoring any errors)
3. rollback - rollback to previous version and attempt deployment.