If you change the names of the orgs in custom spec.yaml minfab up command fails

[vipinsun]

Verify the organization option ****************************** Default option org is org0.example.com which does not exist in your spec, use -o to specify one

#stats minifab: ok=19 failed=1

Specifying -o with an existing org name (which exists in the custom spec.yaml) works

The failure is probably due to the hard-coded default org name only to be overridden by the -o flag

This failure has knock-on effects as the minifab cleanup does not work either and you have to manually remove the files Suggested fix is to get the first org as the default org, unless of course overridden by the -o flag (which does work now)

Maybe the real fix is to override the envsettings file. Unfortunately, this file unlike the spec-yaml file is copied from the vars directory which gets cleanedup when you run cleanup Also you are not supposed to change this file.

[litong01]

That is right. Guess what the user really wants to do is hard. It is really better leaving this to user to specify the org since user already customized the spec and the error msg clearly indicates what is wrong. I think there is no need to do extra on this.

[vipinsun]

Other effects are not being able to do ccup as the code fails with null channel name (even though channel name is in the envsettings)

[Anil8753]

@vipinsun That's why -o is there. I do not think it is worth spending time on. I am using minifabric with custom Orgs names and never face any issue, just need to ensure what I am passing in -o switch.

[vipinsun]

There are legitimate reasons for taking overrides from environment. That is why spec.yaml has been created. These philosophic differences are in every configuration driven app. Minifab's whole purpose is automation and driving the integrity of configuration. Spending time is a choice to improve the user experience, not simply of expediency.