Skip to content

docs(ec2_image_builder): implementation proposal#133

Open
rpocase wants to merge 1 commit intocanonical:mainfrom
rpocase:20260303-component-builder-specification
Open

docs(ec2_image_builder): implementation proposal#133
rpocase wants to merge 1 commit intocanonical:mainfrom
rpocase:20260303-component-builder-specification

Conversation

@rpocase
Copy link
Contributor

@rpocase rpocase commented Mar 3, 2026

ec2_image_builder supports marketplace like listings and is fully supported for seller use cases (both paid and free). this adds a proposed implementation architecture
that is backwards compatible with AmiProducts but keeps a consistent look and feel

- eu-west-1
future_region_support: true

offer:
Copy link
Contributor

Choose a reason for hiding this comment

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

This doesn't need to be under ec2-image-builder field. using the same offer api.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

it still needs a specific key because it isn't nested alongside an existing ami product. the models will reuse the existing offer structure, though

#### Full schema example

```yaml
ec2_image_builder:
Copy link
Contributor

Choose a reason for hiding this comment

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

im a bit confused about why we need a separate ec2_image_builder field instead of keeping it under product. the only difference seems to be the version field, which we need to support the DeliveryOption for Ec2ImageBuilderComponent.

would it be possible to keep the existing structure and modify only the version field instead?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

you could perhaps inherit and override version, but i prefer to be explicit here over having the redirect. if there were more model validations directly in AmiProduct i would be more worried about it

refund_policy: |
Your refund policy.

version:
Copy link
Contributor

Choose a reason for hiding this comment

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

i would like to suggest changing only this field by adding a delivery_options field and allowing the driver and changeset to handle it accordingly.

another question: do we want to support multiple version requests? if so, we would need to implement that capability in both the driver and the changeset as well.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

i think that IBVersion will handle this appropriately. is there something i am missing?

@rpocase rpocase force-pushed the 20260303-component-builder-specification branch from d515d13 to 76ddc8f Compare March 10, 2026 07:07
ec2_image_builder supports marketplace like listings and is fully supported
for seller use cases (both paid and free). this adds a proposed implementation architecture
  that is backwards compatible with AmiProducts but keeps a consistent look and feel
@rpocase rpocase force-pushed the 20260303-component-builder-specification branch from 76ddc8f to 5ca22e9 Compare March 10, 2026 07:15
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.

2 participants