Organisations

By default, nf aerocloud v7 commands operate within your personal workspace. If you are a member of one or more organisations, you can make them operate within an organisation instead.

List your organisations

nf aerocloud org list

This lists the organisations you are a member of, along with their ids. Pass --members (or -m) to also show the members of each organisation.

Set a default organisation

Save a default organisation in the config, so every v7 command operates within it:

nf aerocloud set-org <ORG_ID>

nf config show displays the default organisation, if any. To go back to your personal workspace by default:

nf aerocloud unset-org

Operate within an organisation

To use a different organisation for a single command, pass --org <ORG_ID> to any v7 command:

nf aerocloud v7 --org <ORG_ID> list-projects

You can also set the NF_AEROCLOUD_ORG environment variable, which is handy in scripts and CI:

export NF_AEROCLOUD_ORG=<ORG_ID>
nf aerocloud v7 list-projects

Operate within your personal workspace

Pass --personal to operate within your personal workspace for a single command, ignoring both --org (or NF_AEROCLOUD_ORG) and the default organisation:

nf aerocloud v7 --personal list-projects

Which workspace is used

The workspace is picked in this order:

1. --personal
2. --org <ORG_ID> or NF_AEROCLOUD_ORG
3. The default organisation set with nf aerocloud set-org
4. Your personal workspace

To avoid surprises, v7 commands print the workspace they operate within before running, e.g. Workspace: org Acme (<ORG_ID>) or Workspace: personal workspace. This line is printed on stderr, so it doesn’t interfere with piping output, and is omitted entirely when --json is set. batch shows the workspace in its headers instead.