Project

Profile

Help

Story #3927

Updated by ttereshc about 6 years ago

As a result of this story the user will be able to upload a set of reports about a consumer. The payload will look like this: 

 <pre> 
 [ 
 { 
   "content_type": "modulemd", 
   "profile": [{"name": "duck", 
                "stream": 0, 
                "version": "20180730233102", 
                "context": "deadbeef", 
                "arch": "noarch", 
                "profiles": ["default"]}, 
                {"name": "flipper", 
                "stream": 0.71, 
                "version": "20180707144203", 
                "context": "c0ffee42", 
                "arch": "x86_64", 
                "profiles": ["default", "server"]} 
                ] 
 } }, 
 </pre> 
 <pre> 
 { 
   "content_type": “rpm", 
   "profile": [ {"name": "duck_the_second", 
                "version": 2, 
                "release”: "livebeef", 
                "arch": "noarch", 
                "epoch": "default", 
                “vendor”:”RH”}, 
                ] 
 } 


 
 ] 

 </pre> 


 The "profiles" field on the actual module object reflects the enabled profiles for that module.  
 Pulp's applicability APIs will then be able to use this profile to calculate applicability to a consumer.  

 Profile for rpm type seems to be the same as before, so no migration is needed.

Back