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

Ability to specify a default source when doing choco push #62

Closed
gep13 opened this issue Feb 4, 2015 · 5 comments · Fixed by #2430
Closed

Ability to specify a default source when doing choco push #62

gep13 opened this issue Feb 4, 2015 · 5 comments · Fixed by #2430
Assignees
Milestone

Comments

@gep13
Copy link
Member

gep13 commented Feb 4, 2015

Use Case:

Default, out of the box, when you do choco push you get a warning about missing source

As a User, I want to be able to specify default source, so I don't have to always do choco push -source http://chocolatey.org/

@gep13 gep13 added this to the 0.9.10 milestone Feb 4, 2015
@ferventcoder
Copy link
Member

Two things here. We start out with chocolatey.org as the default as well?

@ferventcoder
Copy link
Member

So no default on OOTB. Like it.

@cwacha
Copy link

cwacha commented Sep 11, 2019

+1

and should be very easy to implement

@julio-92
Copy link

@ferventcoder is anyone working on this? I ran into this as a user and was thinking of giving it a try.

TheCakeIsNaOH added a commit to TheCakeIsNaOH/choco that referenced this issue Oct 29, 2021
This config value will be used to set the default source used for
choco push. The default value will be overridden if the user specifies
--source. The value goes into config.PushCommand.DefaultSource
TheCakeIsNaOH added a commit to TheCakeIsNaOH/choco that referenced this issue Oct 29, 2021
If the DefaultPushSource config value is not empty, use it as the
default source which to push packages. Using --source will override
it. It overrides the built-in default of using the
"ChocolateyCommunityFeedPushSource".

If --api-key is not passed and a api key has not been saved for the
DefaultPushSource, it will fail with the standard message about an api
key being required.
TheCakeIsNaOH added a commit to TheCakeIsNaOH/choco that referenced this issue Oct 29, 2021
If the DefaultPushSource is set to "disabled", this will throw an error
message saying that an source must be specified in the command.

As DefaultPushSource overrides the built-in default of
"ChocolateyCommunityFeedPushSource", the end behavior is that if it is
set to "disabled", then a source must be passed with --source.

This behavior is useful if a user wants has multiple repositories and
wants to always have to explicitly specify a source so as to make sure
to push package to the correct source.
TheCakeIsNaOH added a commit to TheCakeIsNaOH/choco that referenced this issue Oct 29, 2021
Adds tests for DefaultPushSource to check it works correctly.

If DefaultPushSource is set, it should set the source assuming that
a source is not passed in explicitly with --source. If a source is
passed in explicitly, then DefaultPushSource should not override it.

If DefaultPushSource is set to "disabled", it should throw an error if
there is not an explicit source passed in. But if an explicit source is
passed in, it should not error.
TheCakeIsNaOH added a commit to TheCakeIsNaOH/choco that referenced this issue Nov 13, 2021
This config value will be used to set the default source used for
choco push. The default value will be overridden if the user specifies
--source. The value goes into config.PushCommand.DefaultSource
TheCakeIsNaOH added a commit to TheCakeIsNaOH/choco that referenced this issue Nov 13, 2021
If the DefaultPushSource config value is not empty, use it as the
default source which to push packages. Using --source will override
it. It overrides the built-in default of using the
"ChocolateyCommunityFeedPushSource".

If --api-key is not passed and a api key has not been saved for the
DefaultPushSource, it will fail with the standard message about an api
key being required.
TheCakeIsNaOH added a commit to TheCakeIsNaOH/choco that referenced this issue Nov 13, 2021
If the DefaultPushSource is set to "disabled", this will throw an error
message saying that an source must be specified in the command.

As DefaultPushSource overrides the built-in default of
"ChocolateyCommunityFeedPushSource", the end behavior is that if it is
set to "disabled", then a source must be passed with --source.

This behavior is useful if a user wants has multiple repositories and
wants to always have to explicitly specify a source so as to make sure
to push package to the correct source.
TheCakeIsNaOH added a commit to TheCakeIsNaOH/choco that referenced this issue Nov 13, 2021
Adds tests for DefaultPushSource to check it works correctly.

If DefaultPushSource is set, it should set the source assuming that
a source is not passed in explicitly with --source. If a source is
passed in explicitly, then DefaultPushSource should not override it.

If DefaultPushSource is set to "disabled", it should throw an error if
there is not an explicit source passed in. But if an explicit source is
passed in, it should not error.
TheCakeIsNaOH added a commit to TheCakeIsNaOH/choco that referenced this issue Dec 24, 2021
This config value will be used to set the default source used for
choco push. The default value will be overridden if the user specifies
--source. The value goes into config.PushCommand.DefaultSource
TheCakeIsNaOH added a commit to TheCakeIsNaOH/choco that referenced this issue Dec 24, 2021
If the DefaultPushSource config value is not empty, use it as the
default source which to push packages. Using --source will override
it. It overrides the built-in default of using the
"ChocolateyCommunityFeedPushSource".

If --api-key is not passed and a api key has not been saved for the
DefaultPushSource, it will fail with the standard message about an api
key being required.
TheCakeIsNaOH added a commit to TheCakeIsNaOH/choco that referenced this issue Dec 24, 2021
If the DefaultPushSource is set to "disabled", this will throw an error
message saying that an source must be specified in the command.

As DefaultPushSource overrides the built-in default of
"ChocolateyCommunityFeedPushSource", the end behavior is that if it is
set to "disabled", then a source must be passed with --source.

This behavior is useful if a user wants has multiple repositories and
wants to always have to explicitly specify a source so as to make sure
to push package to the correct source.
TheCakeIsNaOH added a commit to TheCakeIsNaOH/choco that referenced this issue Dec 24, 2021
Adds tests for DefaultPushSource to check it works correctly.

If DefaultPushSource is set, it should set the source assuming that
a source is not passed in explicitly with --source. If a source is
passed in explicitly, then DefaultPushSource should not override it.

If DefaultPushSource is set to "disabled", it should throw an error if
there is not an explicit source passed in. But if an explicit source is
passed in, it should not error.
TheCakeIsNaOH added a commit to TheCakeIsNaOH/choco that referenced this issue Jan 17, 2022
This config value will be used to set the default source used for
choco push. The default value will be overridden if the user specifies
--source. The value goes into config.PushCommand.DefaultSource
TheCakeIsNaOH added a commit to TheCakeIsNaOH/choco that referenced this issue Jan 17, 2022
If the DefaultPushSource config value is not empty, use it as the
default source which to push packages. Using --source will override
it. It overrides the built-in default of using the
"ChocolateyCommunityFeedPushSource".

If --api-key is not passed and a api key has not been saved for the
DefaultPushSource, it will fail with the standard message about an api
key being required.
TheCakeIsNaOH added a commit to TheCakeIsNaOH/choco that referenced this issue Dec 22, 2022
This config value will be used to set the default source used for
choco push. The default value will be overridden if the user specifies
--source. The value goes into config.PushCommand.DefaultSource
TheCakeIsNaOH added a commit to TheCakeIsNaOH/choco that referenced this issue Dec 22, 2022
If the DefaultPushSource config value is not empty, use it as the
default source which to push packages. Using --source will override
it. It overrides the built-in default of using the
"ChocolateyCommunityFeedPushSource".

If --api-key is not passed and a api key has not been saved for the
DefaultPushSource, it will fail with the standard message about an api
key being required.
TheCakeIsNaOH added a commit to TheCakeIsNaOH/choco that referenced this issue Dec 22, 2022
If the DefaultPushSource is set to "disabled", this will throw an error
message saying that an source must be specified in the command.

As DefaultPushSource overrides the built-in default of
"ChocolateyCommunityFeedPushSource", the end behavior is that if it is
set to "disabled", then a source must be passed with --source.

This behavior is useful if a user wants has multiple repositories and
wants to always have to explicitly specify a source so as to make sure
to push package to the correct source.
TheCakeIsNaOH added a commit to TheCakeIsNaOH/choco that referenced this issue Dec 22, 2022
Adds tests for DefaultPushSource to check it works correctly.

If DefaultPushSource is set, it should set the source assuming that
a source is not passed in explicitly with --source. If a source is
passed in explicitly, then DefaultPushSource should not override it.

If DefaultPushSource is set to "disabled", it should throw an error if
there is not an explicit source passed in. But if an explicit source is
passed in, it should not error.

If the DefaultPushSource is set to the name/alias of a machine source,
it should resolve to that machine source.
TheCakeIsNaOH added a commit to TheCakeIsNaOH/choco that referenced this issue Jan 7, 2023
This config value will be used to set the default source used for
choco push. The default value will be overridden if the user specifies
--source. The value goes into config.PushCommand.DefaultSource
TheCakeIsNaOH added a commit to TheCakeIsNaOH/choco that referenced this issue Jan 7, 2023
If the DefaultPushSource config value is not empty, use it as the
default source which to push packages. Using --source will override
it. It overrides the built-in default of using the
"ChocolateyCommunityFeedPushSource".

If --api-key is not passed and a api key has not been saved for the
DefaultPushSource, it will fail with the standard message about an api
key being required.
TheCakeIsNaOH added a commit to TheCakeIsNaOH/choco that referenced this issue Jan 7, 2023
If the DefaultPushSource is set to "disabled", this will throw an error
message saying that an source must be specified in the command.

As DefaultPushSource overrides the built-in default of
"ChocolateyCommunityFeedPushSource", the end behavior is that if it is
set to "disabled", then a source must be passed with --source.

This behavior is useful if a user wants has multiple repositories and
wants to always have to explicitly specify a source so as to make sure
to push package to the correct source.
TheCakeIsNaOH added a commit to TheCakeIsNaOH/choco that referenced this issue Jan 7, 2023
Adds tests for DefaultPushSource to check it works correctly.

If DefaultPushSource is set, it should set the source assuming that
a source is not passed in explicitly with --source. If a source is
passed in explicitly, then DefaultPushSource should not override it.

If DefaultPushSource is set to "disabled", it should throw an error if
there is not an explicit source passed in. But if an explicit source is
passed in, it should not error.

If the DefaultPushSource is set to the name/alias of a machine source,
it should resolve to that machine source.
TheCakeIsNaOH added a commit to TheCakeIsNaOH/choco that referenced this issue Jan 13, 2023
This config value will be used to set the default source used for
choco push. The default value will be overridden if the user specifies
--source. The value goes into config.PushCommand.DefaultSource
TheCakeIsNaOH added a commit to TheCakeIsNaOH/choco that referenced this issue Jan 13, 2023
If the DefaultPushSource config value is not empty, use it as the
default source which to push packages. Using --source will override
it. It overrides the built-in default of using the
"ChocolateyCommunityFeedPushSource".

If --api-key is not passed and a api key has not been saved for the
DefaultPushSource, it will fail with the standard message about an api
key being required.
TheCakeIsNaOH added a commit to TheCakeIsNaOH/choco that referenced this issue Jan 13, 2023
If the DefaultPushSource is set to "disabled", this will throw an error
message saying that an source must be specified in the command.

As DefaultPushSource overrides the built-in default of
"ChocolateyCommunityFeedPushSource", the end behavior is that if it is
set to "disabled", then a source must be passed with --source.

This behavior is useful if a user wants has multiple repositories and
wants to always have to explicitly specify a source so as to make sure
to push package to the correct source.
TheCakeIsNaOH added a commit to TheCakeIsNaOH/choco that referenced this issue Jan 13, 2023
Adds tests for DefaultPushSource to check it works correctly.

If DefaultPushSource is set, it should set the source assuming that
a source is not passed in explicitly with --source. If a source is
passed in explicitly, then DefaultPushSource should not override it.

If DefaultPushSource is set to "disabled", it should throw an error if
there is not an explicit source passed in. But if an explicit source is
passed in, it should not error.

If the DefaultPushSource is set to the name/alias of a machine source,
it should resolve to that machine source.
@gep13 gep13 modified the milestones: 1.x, 2.0.0 Feb 3, 2023
TheCakeIsNaOH added a commit to TheCakeIsNaOH/choco that referenced this issue Mar 16, 2023
This config value will be used to set the default source used for
choco push. The default value will be overridden if the user specifies
--source. The value goes into config.PushCommand.DefaultSource
TheCakeIsNaOH added a commit to TheCakeIsNaOH/choco that referenced this issue Mar 16, 2023
If the DefaultPushSource config value is not empty, use it as the
default source which to push packages. Using --source will override
it. It overrides the built-in default of using the
"ChocolateyCommunityFeedPushSource".

If --api-key is not passed and a api key has not been saved for the
DefaultPushSource, it will fail with the standard message about an api
key being required.
TheCakeIsNaOH added a commit to TheCakeIsNaOH/choco that referenced this issue Mar 16, 2023
If the DefaultPushSource is set to "disabled", this will throw an error
message saying that an source must be specified in the command.

As DefaultPushSource overrides the built-in default of
"ChocolateyCommunityFeedPushSource", the end behavior is that if it is
set to "disabled", then a source must be passed with --source.

This behavior is useful if a user wants has multiple repositories and
wants to always have to explicitly specify a source so as to make sure
to push package to the correct source.
TheCakeIsNaOH added a commit to TheCakeIsNaOH/choco that referenced this issue Mar 16, 2023
Adds tests for DefaultPushSource to check it works correctly.

If DefaultPushSource is set, it should set the source assuming that
a source is not passed in explicitly with --source. If a source is
passed in explicitly, then DefaultPushSource should not override it.

If DefaultPushSource is set to "disabled", it should throw an error if
there is not an explicit source passed in. But if an explicit source is
passed in, it should not error.

If the DefaultPushSource is set to the name/alias of a machine source,
it should resolve to that machine source.
vexx32 pushed a commit to TheCakeIsNaOH/choco that referenced this issue Mar 17, 2023
This config value will be used to set the default source used for
choco push. The default value will be overridden if the user specifies
--source. The value goes into config.PushCommand.DefaultSource
vexx32 pushed a commit to TheCakeIsNaOH/choco that referenced this issue Mar 17, 2023
If the DefaultPushSource config value is not empty, use it as the
default source which to push packages. Using --source will override
it. It overrides the built-in default of using the
"ChocolateyCommunityFeedPushSource".

If --api-key is not passed and a api key has not been saved for the
DefaultPushSource, it will fail with the standard message about an api
key being required.
vexx32 pushed a commit to TheCakeIsNaOH/choco that referenced this issue Mar 17, 2023
If the DefaultPushSource is set to "disabled", this will throw an error
message saying that an source must be specified in the command.

As DefaultPushSource overrides the built-in default of
"ChocolateyCommunityFeedPushSource", the end behavior is that if it is
set to "disabled", then a source must be passed with --source.

This behavior is useful if a user wants has multiple repositories and
wants to always have to explicitly specify a source so as to make sure
to push package to the correct source.
vexx32 pushed a commit to TheCakeIsNaOH/choco that referenced this issue Mar 17, 2023
Adds tests for DefaultPushSource to check it works correctly.

If DefaultPushSource is set, it should set the source assuming that
a source is not passed in explicitly with --source. If a source is
passed in explicitly, then DefaultPushSource should not override it.

If DefaultPushSource is set to "disabled", it should throw an error if
there is not an explicit source passed in. But if an explicit source is
passed in, it should not error.

If the DefaultPushSource is set to the name/alias of a machine source,
it should resolve to that machine source.
vexx32 added a commit that referenced this issue Mar 17, 2023
@gep13 gep13 added 4 - Done and removed 3 - Review labels Mar 21, 2023
@pauby pauby changed the title Ability to specify a default source when doing choco push Ability to specify a default source when doing choco push May 31, 2023
@choco-bot
Copy link

🎉 This issue has been resolved in version 2.0.0 🎉

The release is available on:

Your GitReleaseManager bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants