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(secgroups): do not null out ingress & egress #128

Merged
merged 2 commits into from
May 8, 2019

Conversation

metral
Copy link
Contributor

@metral metral commented May 4, 2019

Fixes #127

  • Note: This PR reverses the default null values used for the
    ingress and egress in-line rules of the secgroups, introduced in v0.18.3.
    The null default was required to move to standalone secgroup rules.
  • Upgrade Path - This is a breaking change unless you do the following steps:
    • If using >= v0.18.3: update using the typical package update path.
    • If using <= v0.18.2:
      1. First, update your cluster from using your current version to v0.18.4.
      2. Next, update your cluster from v0.18.4 to v0.18.5 (or higher) using the typical package update path.

@metral metral requested a review from lukehoban May 4, 2019 20:35
@naineel
Copy link
Contributor

naineel commented May 7, 2019

Just hit this myself

Copy link
Member

@lukehoban lukehoban left a comment

Choose a reason for hiding this comment

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

LGTM.

CHANGELOG.md Outdated Show resolved Hide resolved
- Note: This PR reverses the default null values used for the
  ingress and egress in-line rules of the secgroups, introduced in `v0.18.3`.
  The null default was required to move to standalone secgroup rules.
- Upgrade Path - This is a breaking change **unless** you do the
following steps:
  - If using >= `v0.18.3`: update using the typical package update path.
  - If using <= `v0.18.2`:
    1. First, update your cluster from using your current version to `v0.18.4`.
    1. Next, update your cluster from `v0.18.4` to `v0.18.5` (or higher) using the typical package update path.
@metral metral force-pushed the metral/fix-secgroup-rule-defaults branch from bd17a63 to 8ccd4d1 Compare May 8, 2019 21:12
@metral metral merged commit d345f7b into master May 8, 2019
@pulumi-bot pulumi-bot deleted the metral/fix-secgroup-rule-defaults branch May 8, 2019 22:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Defaulting the secgroups in-line rules to null creates empty secgroups on a cluster replacement
3 participants