Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: do not add the cache access policy if there is none #540

Merged
merged 2 commits into from
Oct 9, 2022

Conversation

kayman-mk
Copy link
Collaborator

@kayman-mk kayman-mk commented Sep 1, 2022

Description

In case the module does not create the cache and var.cache_bucket["policy"] is empty, the module can't be deployed as explained in #528 (comment).

This PR makes sure to add the policy only if it exists.

Migrations required

No.

Verification

  • Deploy the module without creating a cache and setting the policy. Module is created without any error.

Copy link
Collaborator

@npalm npalm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And once again thanks for your contribution!

@npalm npalm merged commit f69c8bb into cattle-ops:develop Oct 9, 2022
semantic-releaser bot pushed a commit that referenced this pull request Oct 9, 2022
## [5.3.0](5.2.2...5.3.0) (2022-10-09)

### Features

* add extra_hosts to config.toml ([#547](#547)) ([1491698](1491698))

### Bug Fixes

* do not add the cache access policy if there is none ([#540](#540)) ([f69c8bb](f69c8bb))
* Too long host names for docker machines ([#549](#549)) ([2fc8e77](2fc8e77))
@semantic-releaser
Copy link
Contributor

🎉 This PR is included in version 5.3.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants