Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@steviecoaster
Copy link
Contributor

This PR addresses a bug where creating a new Deployment step throws a 400 error.
The endpoints for Basic and Advanced are slightly different, and Basic requires the choco command be lowercase.

Fixes #28


try{
$null = Invoke-RestMethod @irmParams -ErrorAction Stop
$null = Invoke-RestMethod @irmParams -ErrorAction Stop -Proxy 'http://127.0.0.1:8888'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@steviecoaster you aren't going to need this part anymore

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Damn it all.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@steviecoaster this still needs to be removed here as well.

@@ -1,107 +1,107 @@
# Add-CCMGroup
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should the entire gen folder be excluded from source control?

GUID = '7097e495-f5e0-4d7f-acba-8e2bbeb354af'

# Author of this module
Author = 'Stephen Valdinger'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we need to remove this file from source control, right?

@gep13
Copy link
Member

gep13 commented Nov 25, 2020

There seems to be a little bit more going on in here than just the fixing of the 400 error. Should we break this into different commits, referencing different issues?

@steviecoaster
Copy link
Contributor Author

Hmm. The gen stuff is in the gitignore. I am probably holding that wrong.

I can break things apart a bit, sure.

@gep13
Copy link
Member

gep13 commented Nov 25, 2020

@steviecoaster if the files were already added to the repository, which it looks like they were, adding the entry into the .gitignore file won't actually do anything. Git can't ignore the files, as they are already in the repository. You would first need to delete all the files, then the entry in the .gitignore file will be respected, and the files won't be added back in again.

@gep13
Copy link
Member

gep13 commented Dec 2, 2020

@steviecoaster did we decide whether or not the generated files should be removed from this repository? If so, I think they still need to be deleted, as they are currently all being edited within this PR.

Were there issues for the other commits that are in this PR? If so, it would be good to add a link to them, and if not, it would be good to get ones added, so that they can form the basis of the release notes for the release.

@steviecoaster
Copy link
Contributor Author

#2 was created and closed for the -All bit, but I missed some tangential calls in other places when that fix was merged in. So, not sure if it worth creating a new issue, and linking to it for this here? If that's the proper thing to do (I think it is), I'll do that and fix things up so that the release notes make sense.

I don't think the generated files have no business here in this repo, they need to go over to the docs repo, (They are, it's just manually as I need this code base to generate them). I believe one of the commits on this PR will remove them from the Repo once this gets merged, if I'm understanding the gits correctly (good chance I'm not).


try{
$null = Invoke-RestMethod @irmParams -ErrorAction Stop
$null = Invoke-RestMethod @irmParams -ErrorAction Stop -Proxy 'http://127.0.0.1:8888'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@steviecoaster this still needs to be removed here as well.

{
param($Command,$Parameter,$WordToComplete,$CommandAst,$FakeBoundParams)
$r = (Get-CCMDeployment -All).Name
$r = (Get-CCMDeployment).Name
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@steviecoaster I don't think that this is meant to be in this commit.

{
param($Command,$Parameter,$WordToComplete,$CommandAst,$FakeBoundParams)
$r = (Get-CCMGroup -All).Name
$r = (Get-CCMGroup).Name
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@steviecoaster I don't think this is meant to be in this commit.

@gep13
Copy link
Member

gep13 commented Dec 3, 2020

@steviecoaster said...
So, not sure if it worth creating a new issue, and linking to it for this here? If that's the proper thing to do (I think it is), I'll do that and fix things up so that the release notes make sense.

Yes, I believe a follow up issue, linking to the first one, would be the best course of action here. Once the issue is created, the commit message in this PR can be updated to point at it.

@steviecoaster said...
I believe one of the commits on this PR will remove them from the Repo once this gets merged

Assuming you are talking about this commit the only changes that I can see being made there is to edit the existing files. They are not yet being deleted from the repository.

Let me know if you want to try to grab some time to go through this.

@gep13
Copy link
Member

gep13 commented Dec 4, 2020

@steviecoaster I have taken the liberty of creating a new PR which I believe addresses some of the concerns that I have raised. All the work that was contained in this PR has been moved into the new PR, and it also addresses some more items.

I would suggest that we close this PR, and begin review on the new PR.

Let me know if you have any questions.

@gep13 gep13 deleted the GH28 branch September 8, 2022 07:02
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.

New-CCMDeploymentStep Throws HTTP 400 Error

3 participants