Bump github.com/operator-framework/operator-sdk from 0.14.1-0.20200114205503-152e5d5bc3a1 to 0.15.2

[dependabot]

Bumps github.com/operator-framework/operator-sdk from 0.14.1-0.20200114205503-152e5d5bc3a1 to 0.15.2.

Release notes

Sourced from github.com/operator-framework/operator-sdk's releases.

v0.15.2

Changed

• Operator user setup and entrypoint scripts no longer insert dynamic runtime user entries into /etc/passwd. To use dynamic runtime users, use a container runtime that supports it (e.g. CRI-O). (#2469)

Bug Fixes

• Fixed a regression in the operator-sdk run command that caused --local flags to be ignored (#2478)

v0.15.1

Bug Fixes

• Fixed issue with Go dependencies caused by removed tag in openshift/api repository (#2466)

v0.15.0

Added

• Added the cleanup subcommand and run --olm to manage deployment/deletion of operators. These commands currently interact with OLM via an in-cluster registry-server created using an operator's on-disk manifests and managed by operator-sdk. (#2402, #2441)
• Added bundle create which builds, and optionally generates metadata for, operator bundle images. (#2076, #2438)
• Added bundle validate which validates operator bundle images. (#2411)

Changed

• Changed error wrapping according to Go version 1.13+ error handling. (#2355)
• Added retry logic to the cleanup function from the e2e test framework in order to allow it to be achieved in the scenarios where temporary network issues are faced. (#2277)
• Breaking Change: Moved olm-catalog gen-csv to the generate csv subcommand. (#2439)
• Breaking Change: run ansible/helm are now the hidden commands exec-entrypoint ansible/helm. All functionality of each subcommand is the same. (#2441)
• Breaking Change: up local is now run --local. All functionality of this command is the same. (#2441)
• Breaking Change: Moved the olm subcommand from alpha to its own subcommand. All functionality of this command is the same. (#2447)

Bug Fixes

• Fixed a regression in the helm-operator that caused all releases to be deployed in the same namespace that the operator was deployed in, regardless of which namespace the CR was created in. Now release resources are created in the same namespace as the CR. (#2414)
• Fix issue when the test-framework would attempt to create a namespace exceeding 63 characters. pkg/test/NewCtx() now creates a unique id instead of using the test name. TestCtx.GetNamespace() uses this unique id to create a namespace that avoids this scenario. (#2335)

Note: See how to upgrade your project to the version v0.15.0 by checking the Version Upgrade Guide

v0.14.1

Bug Fixes

• Fixed a regression in the helm-operator that caused all releases to be deployed in the same namespace that the operator was deployed in, regardless of which namespace the CR was created in. Now release resources are created in the same namespace as the CR. (#2414)

Note: See how to upgrade your project to the version v0.14.1 by checking the Version Upgrade Guide

Changelog

Sourced from github.com/operator-framework/operator-sdk's changelog.

v0.15.2

Changed

• Operator user setup and entrypoint scripts no longer insert dynamic runtime user entries into /etc/passwd. To use dynamic runtime users, use a container runtime that supports it (e.g. CRI-O). (#2469)

Bug Fixes

• Fixed a regression in the operator-sdk run command that caused --local flags to be ignored (#2478)

v0.15.1

Bug Fixes

• Fixed issue with Go dependencies caused by removed tag in openshift/api repository (#2466)

v0.15.0

Added

• Added the cleanup subcommand and run --olm to manage deployment/deletion of operators. These commands currently interact with OLM via an in-cluster registry-server created using an operator's on-disk manifests and managed by operator-sdk. (#2402, #2441)
• Added bundle create which builds, and optionally generates metadata for, operator bundle images. (#2076, #2438)
• Added bundle validate which validates operator bundle images. (#2411)

Changed

• Changed error wrapping according to Go version 1.13+ error handling. (#2355)
• Added retry logic to the cleanup function from the e2e test framework in order to allow it to be achieved in the scenarios where temporary network issues are faced. (#2277)
• Breaking Change: Moved olm-catalog gen-csv to the generate csv subcommand. (#2439)
• Breaking Change: run ansible/helm are now the hidden commands exec-entrypoint ansible/helm. All functionality of each subcommand is the same. (#2441)
• Breaking Change: up local is now run --local. All functionality of this command is the same. (#2441)
• Breaking Change: Moved the olm subcommand from alpha to its own subcommand. All functionality of this command is the same. (#2447)

Deprecated

Removed

Bug Fixes

• Fixed a regression in the helm-operator that caused all releases to be deployed in the same namespace that the operator was deployed in, regardless of which namespace the CR was created in. Now release resources are created in the same namespace as the CR. (#2414)
• Fix issue when the test-framework would attempt to create a namespace exceeding 63 characters. pkg/test/NewCtx() now creates a unique id instead of using the test name. TestCtx.GetNamespace() uses this unique id to create a namespace that avoids this scenario. (#2335)

v0.14.1

Bug Fixes

• Fixed a regression in the helm-operator that caused all releases to be deployed in the same namespace that the operator was deployed in, regardless of which namespace the CR was created in. Now release resources are created in the same namespace as the CR. (#2414)

v0.14.0

Added

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.