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

Fix documentation #174

Merged
merged 1 commit into from
Feb 2, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions .web-docs/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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/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/osc/bsu). It is much easier to use and Outscale generally recommends BSU-backed images nowadays.

- [outscale-bsu](/packer/integrations/outscale/outscale/latest/components/builder/bsu) - Create BSU-backed OMIs by
- [outscale-bsu](/packer/integrations/outscale/outscale/latest/components/builder/osc/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.
Expand All @@ -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/bsusurrogate) - Create BSU-backed OMIs from scratch. Works similarly to the `chroot` builder but does
- [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
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/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/osc/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.
Expand Down
8 changes: 4 additions & 4 deletions docs/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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/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/osc/bsu). It is much easier to use and Outscale generally recommends BSU-backed images nowadays.

- [outscale-bsu](/packer/integrations/outscale/outscale/latest/components/builder/bsu) - Create BSU-backed OMIs by
- [outscale-bsu](/packer/integrations/outscale/outscale/latest/components/builder/osc/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.
Expand All @@ -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/bsusurrogate) - Create BSU-backed OMIs from scratch. Works similarly to the `chroot` builder but does
- [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
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/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/osc/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.
Expand Down
Loading