Why Octopus provides 2 ways to do the same thing?

Legacy Uncategorised
1

Hi,

According to Octopus documentation the following is the way to create web sites and app pools:

Then I go to the octopus library and you offer there the same thing:
https://library.octopusdeploy.com/#!/step-template/actiontemplate-iis-apppool-create
https://library.octopusdeploy.com/#!/step-template/actiontemplate-iis-website-create

When should I use 1 or another way?

Thanks,
Miguel

2

Hi Miguel,

Thanks for reaching out. The most popular of those 2 is the first one, as most of the times your want to deploy a nuget package and create site/app at the same time. There are cases though where you might wanna just create site/app, without having to deploy a Nuget package. For the latter, you’d use the library steps.

Regards,
Dalmiro

3

Hi Dalmiro,

I also noticed that the second way allows more Parameters, so is more powerful.

What if I’m using method 1, create 15 projects in my company in that way, and later find out that I needed one of the parameters available only in way 2?

Thanks,
Miguel

4

Well since I’m getting no more replies, I’ll advance with the option 2 since it looks more powerful, also because it looks like libraries are always ahead of new octopus releases, and also because if there are updates in these libraries we don’t need to do an Octopus upgrade (which would be needed for new functionalities in option 1).

Thanks,
Miguel

5

Hi Miguel,

If you find that the library steps have some functionalities that you actually need and the Nuget Step lacks those, its absolutely fine to use the first ones.

Regards,
Dalmiro