[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

[Pulp-list] Package APIs



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Below is what I'm currently thinking for the package APIs (these don't
have anything on groups). Create is already in the repo apis under
upload; I don't think we currently have a use case where we'd want to
create a PackageVersion doc without the actual RPM bits. Thoughts?

/packages/
GET    -  List of all package names

/packages/<name>
GET    -  All package versions for that package name
DELETE -  Delete all package versions for that package name

/packages/<name>/<version>/<release>/<epoch>/<arch>
GET    -  Package version details for that package version
DELETE -  Delete the specific package version identified


As a side note, I think we should agree on the order we expect
version/release/epoch to appear so the API is consistent (the actual
*Api classes already differ). I'm thinking we use that order since that
is (to my understanding) the priority of what they represent. Am I
looking at that right or does another order make sense?


- -- 
Jason Dobies
RHCE# 805008743336126
Freenode: jdob
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJMDnAkAAoJEOMmcTqOSQHCw9sIAJbEJgk5cYtbOLBMHjoVUkim
TmdeAGGUGcp7/eDhJY0s1Y2txkgTEbq0j2FSRH9FsHXGkZKPtQwJJrrDswYMV2S0
X1WtY1GrnRy4c8keFipFYLy/Qh7d+TEvA/7U6HAPaeH5y8dfRAjAowSK1W+3uQLM
H35Oh8dwf3FiaGQBQWrVB2kwmB/fuzAxtwh/FhBAp7tyVUv8yFhYRnCAjNcjIJ4P
pZ2cSqSCmt1TiuLFyr26LDCZN0IImWymdK7oarqhda8G9JbT/V2j8SyfhfBJTW6d
sChUkHWQWj4m5jNbWicR1GJNqTWgfy+KyXSD7TtUqxOKz2bXwfquQyDwtjMMWqc=
=LW69
-----END PGP SIGNATURE-----


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]