Bug #18519

Default SCAP content should be uploaded without the user running a rake command

Added by Ondřej Pražák 3 months ago. Updated 3 months ago.

Status:NewSpent time:-
Priority:Normal
Assigned To:-
Category:-
Target version:Foreman - Team Marek backlog
Difficulty: Bugzilla link:1362657
Found in release: Pull request:
Triaged:No
Story points-
Velocity based estimate-

Description

It would make sense to run the 'foreman-rake foreman_openscap:bulk_upload:default' command, which is needed to upload the SCAP content automatically. This allows the user to get up and running more quickly.

Version-Release number of selected component (if applicable):

foreman-1.11.0.49-1.el7sat.noarch
puppet-foreman_scap_client-0.3.3-10.el7sat.noarch
rubygem-openscap-0.4.3-3.el7sat.noarch
rubygem-smart_proxy_openscap-0.5.3.6-1.el7sat.noarch
scap-security-guide-0.1.25-3.el7.noarch
tfm-rubygem-foreman_openscap-0.5.3.17-1.el7sat.noarc

We used to call foreman-rake db:seed in the post install of the SCAP packages. A similar model could work again.

History

#1 Updated by Ondřej Pražák 3 months ago

  • Subject changed from Default SCAP content should be uploaded without the user running a rake command to Default SCAP content should be uploaded without the user running a rake command
  • Target version set to Team Marek backlog

Also available in: Atom PDF