A notice function with a hash as a title causes catalog validation to fail #205
Labels
Comments
|
On further investigation the issue was down to the hash being used on the notice function which broke the validation, replacing these notices with notify resource calls fixed our issue. class iaas_linux_ibm_tivoli_monitoring_client (
Array[Hash] $gateway_list = [ { primary => 'hostname.dopmainname',
standby => 'hostname.domainname' } ],
) {
$gateways = $::iaas_linux_ibm_tivoli_monitoring_client::gateway_list
$rand = fqdn_rand(length($gateways))
notice($gateways[$rand])
$randomly_chosen_gateways = $gateways[$rand]
notice("Choosen gateways list: ${randomly_chosen_gateways}") |
|
@davidsandilands I can reproduce this problem-- failing CI run: https://github.com/github/octocatalog-diff/commit/40a1c8b5eb1dffd6b8500050b14cd1d7c1d6a54b/checks?check_suite_id=289284170 failing test case: 40a1c8b I'm curious - does the failing "notify called with a hash parameter" both compile and execute successfully on a host in your fleet? I'm wondering if this behavior is actually supported by puppet servers and clients in the wild - or maybe it only works with certain formats of catalogs? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Running octocatalog-diff
Catalog failed to compile with invalid json
Catalog to compile
Create an array of hashes and call one of those hashes.
ie
The text was updated successfully, but these errors were encountered: