Table of contents
- SUSE Studio Help
- SUSE Studio API
- Libraries & Clients
- Using the API with curl
- SUSE Studio User API v2.0
- More information
- How to contribute
- Legal Information
Returns information about the account, such as username, email address and disk quota.
Returns the running API version including the minor version.
Studio returns several types of return values:
XML according to the call documentation above,
a success message:
one of many error results, which contain a
message. You will find an example at the bottom of the list.
- For whatever reason, you do not have permission to do whatever it is you’re trying to do.
- We can’t find the build you’ve asked for.
- You can’t delete a published build, so unpublish it and try again.
- Something has gone horribly wrong and we can’t build your appliance.
- We couldn’t download the file you’ve asked us to download.
- You’ve already built a specific version of an appliance, so you’ll need to force an overwrite if you want to keep going.
- You can’t rebuild appliances that have been published to the Gallery.
- You’ll need to wait until the first build of an appliance is done before building additional image types.
- Something went wrong inside Studio, and it’s probably not your fault. The error message will tell you more.
- You can’t build ARM appliances yet, sorry.
- That won’t, either.
- You’ve requested a build of an appliance that doesn’t exist.
- You can only upload RPMs or tarballs with RPMs in them.
- We can’t find the GPG key that you’re looking for.
- Sometimes you get to specify which type of image (ISO, VMX, etc.) you’d like. And sometimes an appliance hasn’t been built in that type.
- The GPG key isn’t going to work out.
- We need a name to import GPG keys.
- An unknown node was found during the parsing of POSTed XML.
- I think that’s clear enough.
- If you try to reply to a comment that doesn’t exist, we’ll tell you.
- You’ve asked for a file that doesn’t exist.
- You can only upload files-via-url that are HTTP(S) or FTP.
- … between 0 and 5.
- If we can’t find the repository, we can’t add it to your appliance.
- Please don’t POST with both
urlparams together, and don’t POST with neither.
- Yep, nor that.
- That too.
- We need a proper target for the GPG key.
- That won’t work.
- Are you trying to share an appliance with a user who doesn’t have an account?
- You’ve POSTed a value that we can’t do anything with.
- You’ve requested a version of an appliance that doesn’t exist.
- You tried to POST XML that was not valid (missing a closing tag, perhaps?)
- It’s already there!
- You’ve forgotten to tell us which appliance you’d like to work with.
- We need a name in order to add a repository.
- Seems you’ve left something out of your call!
- If you want to rate an appliance, you’ll need to provide a value…
- We need a URL in order to add a repository.
- Sometimes we need to know which version of an appliance you’re intending to GET or modify.
- We’re at full capacity, so you’ll need to come back later.
- We can’t gain access to the file you’ve requested.
- You can’t modify appliances at the moment, please try again later.
- Someone got there first.
- You need to accept some legal stuff before you can build and distribute SLE appliances.
- A generic “catch all” when we don’t have a more descriptive code to offer. The error message will tell you more.
- When you’re searching for appliances in Gallery, you should use the queries we list.
- You’ve tried to add a user repository, but we can’t find one.
- Not all versions of appliances have been published.
- … and sometimes you try to publish an appliance that is already on Gallery.
- You are POSTing when you should be GETting, or some other combination.