Update to ACK runtime v0.56.0, code-generator v0.56.0

[ack-bot]

Update to ACK runtime v0.56.0, code-generator v0.56.0

---

• ACK code-generator v0.56.0 release notes
• ACK runtime v0.56.0 release notes

---

NOTE:
This PR increments the release version of service controller from v1.1.2 to v1.2.0

Once this PR is merged, release v1.2.0 will be automatically created for ssm-controller

Please close this PR, if you do not want the new patch release for ssm-controller

---

stdout for make build-controller:

building ack-generate ... ok.
==== building ssm-controller ====
Copying common custom resource definitions into ssm
Building Kubernetes API objects for ssm
Generating deepcopy code for ssm
Generating custom resource definitions for ssm
Building service controller for ssm
Running GO mod tidy
Generating RBAC manifests for ssm
Running gofmt against generated code for ssm
Updating additional GitHub repository maintenance files
==== building ssm-controller release artifacts ====
Building release artifacts for ssm-v1.2.0
Generating common custom resource definitions
Generating custom resource definitions for ssm
Generating RBAC manifests for ssm

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

To fix this issue, we should add an explicit permissions block at the top level of the workflow file. As per best practice, we should use the most restrictive set required. Since this workflow is delegating its job using uses: to a reusable workflow, there may not be a need for any write permissions at all. The minimal safe starting point is to use permissions: {} which disables all GITHUB_TOKEN permissions for the initial workflow and jobs unless specifically required. This block should be added after the name key or before the on block at the beginning of .github/workflows/postsubmit.yaml.

---

[a-hilaly]

/lgtm

[ack-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: a-hilaly, ack-bot

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [a-hilaly]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment