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.

Sign up for GitHub

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

Jump to bottom

Fixed defining different security.yml was not supported #22

Merged
merged 1 commit into from
Mar 21, 2017
Merged

Fixed defining different security.yml was not supported #22

merged 1 commit into from
Mar 21, 2017

Conversation

Toflar
Copy link
Member

@Toflar Toflar commented Mar 2, 2017

No description provided.

@aschempp
Copy link
Member

aschempp commented Mar 3, 2017

Would that not result in an error when the manager bundle loads security again?

@Toflar
Copy link
Member Author

Toflar commented Mar 3, 2017

I didn't check why but it doesn't.

@aschempp aschempp added the bug label Mar 6, 2017
@aschempp aschempp added this to the 4.3.6 milestone Mar 6, 2017
@leofeyer leofeyer merged commit e2c7533 into hotfix/4.3.6 Mar 21, 2017
@leofeyer leofeyer deleted the fix-security-yml branch March 21, 2017 12:55
leofeyer added a commit that referenced this pull request Mar 21, 2017
@leofeyer
Revert "Support using a custom security.yml file (see #22)."
8edc7c9 
This reverts commit e2c7533.
@aschempp aschempp mentioned this pull request Mar 21, 2017
Closed
@leofeyer
Copy link
Member

See #24.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@leofeyer leofeyer leofeyer approved these changes

Assignees

@Toflar Toflar

@leofeyer leofeyer

Labels
bug
Projects
None yet
Milestone
4.3
Development

Successfully merging this pull request may close these issues.

None yet
3 participants
@Toflar @aschempp @leofeyer