Skip to content

MaxMemoryPolicy should exists as deprecated parameter and throw proper exception when used #951

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

Merged
merged 6 commits into from
Sep 29, 2015
Merged

Conversation

SiddharthChatrolaMs
Copy link
Contributor

MaxMemoryPolicy should exists as deprecated parameter and throw proper exception when used

@azurecla
Copy link

Hi @SiddharthChatrolaMs, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.azure.com.

TTYL, AZPRBOT;

@markcowl
Copy link
Member

@SiddharthChatrolaMs There are merge conflicts, please update

Conflicts:
	src/ResourceManager/RedisCache/Commands.RedisCache/Commands/SetAzureRedisCache.cs
@SiddharthChatrolaMs
Copy link
Contributor Author

Resolved merge conflicts and updated pull request.

stankovski added a commit that referenced this pull request Sep 29, 2015
 MaxMemoryPolicy should exists as deprecated parameter and throw proper exception when used
@stankovski stankovski merged commit e2ba4d4 into Azure:dev Sep 29, 2015
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.

4 participants