Skip to content

prepare-device: add Model Service reference URL#141

Merged
alfonsosanchezbeato merged 2 commits intocanonical:24from
dilyn-corner:add-model-service-url
Apr 13, 2026
Merged

prepare-device: add Model Service reference URL#141
alfonsosanchezbeato merged 2 commits intocanonical:24from
dilyn-corner:add-model-service-url

Conversation

@dilyn-corner
Copy link
Copy Markdown
Contributor

The Model Service should be accessed using its proper URL. A forward will generally be setup from the legacy Serial Vault URL to the new Model Service as part of the Model Service provisioning process, but you should aim to use the proper URL whenever possible. New customers being onboarded shouldn't have a Serial Vault at all, so the serial-vault-partners URL won't be helpful to them.

There are a few other changes currently in-flight which should coincide with this one happening, though I'd argue this takes precedent.

canonical/brand-store-documentation#111
canonical/ubuntu-core-docs#337
canonical/snap-docs#259

The Model Service should be accessed using its proper URL. A forward
will generally be setup from the legacy Serial Vault URL to the new
Model Service as part of the Model Service provisioning process,
but you should aim to use the proper URL whenever possible. New
customers being onboarded shouldn't have a Serial Vault at all, so the
serial-vault-partners URL won't be helpful to them.

Signed-off-by: Dilyn Corner <dilyn@dilyn.cc>
Copy link
Copy Markdown
Member

@alfonsosanchezbeato alfonsosanchezbeato left a comment

Choose a reason for hiding this comment

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

Thanks for this - small nit

Comment thread snap/hooks/prepare-device Outdated
snapctl set registration.proposed-serial="\"$(date -u)\""

# If you are using the Model Service, use the below:
snapctl set device-service.url="https://api.snapcraft.io/v1/"
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

This is fine, but I would prefer to have the two options commented out instead of both uncommented

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Fair. Commented out both and tweaked the comment (s/use/uncomment/).

Users should know which is appropriate and uncomment accordingly.

Signed-off-by: Dilyn Corner <dilyn@dilyn.cc>
Copy link
Copy Markdown
Member

@alfonsosanchezbeato alfonsosanchezbeato left a comment

Choose a reason for hiding this comment

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

Thanks!

@alfonsosanchezbeato alfonsosanchezbeato merged commit d6f75c1 into canonical:24 Apr 13, 2026
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