[FOLIO-1185] folio.yml for folio-ansible refers to deprecated roles Created: 09/Apr/18  Updated: 12/Nov/18  Resolved: 10/Apr/18

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Bug Priority: P3
Reporter: Wayne Schneider Assignee: Wayne Schneider
Resolution: Done Votes: 0
Labels: ci, sprint36
Remaining Estimate: Not Specified
Time Spent: 2 hours, 30 minutes
Original estimate: Not Specified

Sprint:

 Description   

folio.yml still refers to deprecated roles, resulting in this error:

ERROR! the role 'mod-configuration-data' was not found in /Volumes/GoogleDrive/My Drive/workspace_gdrive/folio-ansible/roles:/etc/ansible/roles:/Volumes/GoogleDrive/My Drive/workspace_gdrive/folio-ansible

The error appears to have been in '/Volumes/GoogleDrive/My Drive/workspace_gdrive/folio-ansible/folio.yml': line 30, column 7, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:

    - mod-auth-data
    - mod-configuration-data
      ^ here

This will break the nightly packer build



 Comments   
Comment by Wayne Schneider [ 09/Apr/18 ]

Offending section of folio.yml (lines 26 ff):

# Provision a host with the sample tenant and data
- hosts: folio-sample-data-stable
  roles:
    - mod-auth-data
    - mod-configuration-data
    - mod-users-data 
    - mod-users-bl-data
    - mod-circulation-data
    - mod-notes-data
    - mod-auth-demo-users
Comment by Wayne Schneider [ 09/Apr/18 ]

Probably what we really need to do is deprecate the stable build entirely, of course.

Comment by Wayne Schneider [ 10/Apr/18 ]

Fixed a few things to allow folio-stable to build if necessary.

Generated at Thu Feb 08 23:11:27 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.