Fix the invalid ACIs on initial creation #156

greg · 2020-04-20T17:01:40Z

greg commented

2020-04-20 17:01:40 +00:00

I found this bug while working on #152 in a VM

This is only executed on initial creation of the instance, the production one is using these fixed ACIs, this was only an issue with the setup

The issue was the ACI was set at the wrong level.

I found this bug while working on #152 in a VM This is only executed on initial creation of the instance, the production one is using these fixed ACIs, this was only an issue with the setup The issue was the ACI was set at the wrong level.

raucao commented

2020-04-20 18:57:08 +00:00

I'm not sure how to review this.

greg commented

2020-04-21 11:22:42 +00:00

I'm merging this one, as they are now the same ACIs as in production

greg closed this pull request

2020-04-21 11:22:53 +00:00

greg deleted branch bugfix/ldap_invalid_aci

2020-04-21 11:23:00 +00:00

greg referenced this issue from a commit

2020-05-15 12:10:50 +00:00

Fix the invalid ACIs on initial creation (for real) Follow-up to #156 I found another issue with the initial ACI creation, while creating a fresh VM. I thought I had fixed it in #156 but I was wrong. This time the ACIs are really set and the code runs successfully. The ACIs are set on the suffix, so modifying it is needed This won't be executed on a server that is already running, this is only done on the initial setup

greg referenced this pull request

2020-05-15 12:11:52 +00:00

Fix the invalid ACIs on initial creation (for real) #165

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: kosmos/chef#156