From 54df6a2df974ed819250f24d13f50edebcd0769b Mon Sep 17 00:00:00 2001 From: "matthias.gatto" Date: Mon, 19 Feb 2024 18:36:09 +0100 Subject: [PATCH] Revert "Fix documentation" It did not fix anything This reverts commit d64dc1009513e132e99b2b76cf5df6507cb1b600. --- .web-docs/README.md | 8 ++++---- docs/README.md | 8 ++++---- 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/.web-docs/README.md b/.web-docs/README.md index f921fb4..6d62fe7 100644 --- a/.web-docs/README.md +++ b/.web-docs/README.md @@ -33,9 +33,9 @@ If you do that, you can remove `required_plugins` from packer file. #### Builders --> **Don't know which builder to use?** If in doubt, use the [osc-bsu builder](/packer/integrations/outscale/outscale/latest/components/builder/osc/bsu). It is much easier to use and Outscale generally recommends BSU-backed images nowadays. +-> **Don't know which builder to use?** If in doubt, use the [osc-bsu builder](/packer/integrations/outscale/outscale/latest/components/builder/bsu). It is much easier to use and Outscale generally recommends BSU-backed images nowadays. -- [outscale-bsu](/packer/integrations/outscale/outscale/latest/components/builder/osc/bsu) - Create BSU-backed OMIs by +- [outscale-bsu](/packer/integrations/outscale/outscale/latest/components/builder/bsu) - Create BSU-backed OMIs by launching a source OMI and re-packaging it into a new OMI after provisioning. If in doubt, use this builder, which is the easiest to get started with. @@ -45,10 +45,10 @@ If you do that, you can remove `required_plugins` from packer file. that device. This is an **advanced builder and should not be used by newcomers**. However, it is also the fastest way to build an EBS-backed OMI since no new OUTSCALE VM needs to be launched. -- [outscale-bsusurrogate](/packer/integrations/outscale/outscale/latest/components/builder/osc/bsusurrogate) - Create BSU-backed OMIs from scratch. Works similarly to the `chroot` builder but does +- [outscale-bsusurrogate](/packer/integrations/outscale/outscale/latest/components/builder/bsusurrogate) - Create BSU-backed OMIs from scratch. Works similarly to the `chroot` builder but does not require running in Outscale VM. This is an **advanced builder and should not be used by newcomers**. -- [outscale-bsuvolume](/packer/integrations/outscale/outscale/latest/components/builder/osc/bsuvolume) - Create EBS volumes by launching a source OMI with block devices mapped. Provision the VM, then destroy it, retaining the EBS volumes. +- [outscale-bsuvolume](/packer/integrations/outscale/outscale/latest/components/builder/bsuvolume) - Create EBS volumes by launching a source OMI with block devices mapped. Provision the VM, then destroy it, retaining the EBS volumes. #### Data Sources - [outscale-omi](/packer/integrations/outscale/outscale/latest/components/data-source/omi) - The Outscale OMI Data source will filter and fetch an Outscale OMI. diff --git a/docs/README.md b/docs/README.md index f921fb4..6d62fe7 100644 --- a/docs/README.md +++ b/docs/README.md @@ -33,9 +33,9 @@ If you do that, you can remove `required_plugins` from packer file. #### Builders --> **Don't know which builder to use?** If in doubt, use the [osc-bsu builder](/packer/integrations/outscale/outscale/latest/components/builder/osc/bsu). It is much easier to use and Outscale generally recommends BSU-backed images nowadays. +-> **Don't know which builder to use?** If in doubt, use the [osc-bsu builder](/packer/integrations/outscale/outscale/latest/components/builder/bsu). It is much easier to use and Outscale generally recommends BSU-backed images nowadays. -- [outscale-bsu](/packer/integrations/outscale/outscale/latest/components/builder/osc/bsu) - Create BSU-backed OMIs by +- [outscale-bsu](/packer/integrations/outscale/outscale/latest/components/builder/bsu) - Create BSU-backed OMIs by launching a source OMI and re-packaging it into a new OMI after provisioning. If in doubt, use this builder, which is the easiest to get started with. @@ -45,10 +45,10 @@ If you do that, you can remove `required_plugins` from packer file. that device. This is an **advanced builder and should not be used by newcomers**. However, it is also the fastest way to build an EBS-backed OMI since no new OUTSCALE VM needs to be launched. -- [outscale-bsusurrogate](/packer/integrations/outscale/outscale/latest/components/builder/osc/bsusurrogate) - Create BSU-backed OMIs from scratch. Works similarly to the `chroot` builder but does +- [outscale-bsusurrogate](/packer/integrations/outscale/outscale/latest/components/builder/bsusurrogate) - Create BSU-backed OMIs from scratch. Works similarly to the `chroot` builder but does not require running in Outscale VM. This is an **advanced builder and should not be used by newcomers**. -- [outscale-bsuvolume](/packer/integrations/outscale/outscale/latest/components/builder/osc/bsuvolume) - Create EBS volumes by launching a source OMI with block devices mapped. Provision the VM, then destroy it, retaining the EBS volumes. +- [outscale-bsuvolume](/packer/integrations/outscale/outscale/latest/components/builder/bsuvolume) - Create EBS volumes by launching a source OMI with block devices mapped. Provision the VM, then destroy it, retaining the EBS volumes. #### Data Sources - [outscale-omi](/packer/integrations/outscale/outscale/latest/components/data-source/omi) - The Outscale OMI Data source will filter and fetch an Outscale OMI.