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

Modify source when attempting to add a source with same name but different URL #88

Closed
rpavlik opened this issue Feb 9, 2015 · 0 comments

Comments

@rpavlik
Copy link

rpavlik commented Feb 9, 2015

Or alternately, provide a flag to "create or modify" and leave the default behavior to fail if you're adding again with a different URL. In all cases, adding with identical name and URL should remain idempotent.

@ferventcoder ferventcoder added this to the 0.9.10 milestone Feb 9, 2015
@ferventcoder ferventcoder changed the title RFE: Modify source when attempting to add a source with same name but different URL Modify source when attempting to add a source with same name but different URL Feb 9, 2015
@ferventcoder ferventcoder modified the milestones: 0.9.9.9, 0.9.10 Sep 21, 2015
@ferventcoder ferventcoder self-assigned this Sep 21, 2015
ferventcoder added a commit that referenced this issue Sep 21, 2015
Modify existing source values if new bits are passed about a source,
such as adding priority.
ferventcoder added a commit that referenced this issue Sep 21, 2015
* stable:
  (GH-417) Choco config command
  (maint) Config output skip by contains password
  (GH-416) Features should contain description
  (GH-88) Modify existing source
  (GH-71) Sources can have explicit priority order
  (maint) resharper team settings
  (maint) Case insensitive String.contains
  (maint) formatting
  (GH-89) Note cpack has been deprecated
  (GH-33) Allow Shutting off checksumming

# Conflicts:
#	src/chocolatey/chocolatey.csproj
#	src/chocolatey/infrastructure.app/builders/ConfigurationBuilder.cs
#
src/chocolatey/infrastructure.app/services/ChocolateyConfigSettingsService.cs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants