bitskrieg's profile - activity

I thought this might be the case. Oh well, perhaps in a future version it will be able to pull in parameters from child templates.

Thanks for taking the time to answer!

I am currently in the process of building out nested heat templates where the master template defines some globally-applicable parameters and then just calls other templates as resources as required:

heat_template_version: 2015-10-15

description: Generic OpenStack Deployment Script

parameters:

  base_string:
    type: string
    label: Base String
    description: The unique string which will form the base of all initial resource names in your deployed environment
    default: changeme
      constraints:
        -  length: { min: 3, max: 10 }
      description: Base name must be between 3 and 10 characters
        -  allowed_pattern: "[a-z]*"
      description: Base name must contain only lower case letters

        ...
      resources:    
          network:
            type: https://bitbucket.org/xxx/xxx/raw/master/heat/network/private.yaml
            properties:
              base_string: { get_param: base_string }

        debian:
          type: https://bitbucket.org/xxx/xxx/raw/master/heat/os/debian.yaml
          depends_on: network
          properties:
            base_string: { get_param: base_string }
            network: { get_attr: [network, name] }

etc. My resource templates look like this:

heat_template_version: 2015-10-15

description: Private Network Deployment Heat Template

parameters:

  base_string:
    type: string
    label: Base String
    description: The unique string which will form the base of all initial resource names in your deployed environment
    default: changeme
    constraints:
      -  length: { min: 3, max: 10 }
         description: Base name must be between 3 and 10 characters
      -  allowed_pattern: "[a-z]*"
         description: Base name must contain only lower case letters

  network_ID:
    type: number
    label: Choose a number between 0 and 255
    description: This will determine your exact network subnet for your deployment
    default: 0
    constraints:
      -  range: { min: 0, max: 255 }

resources:

  random-str:
    type: OS::Heat::RandomString
    properties:
      length: 3  

  network:
    type: OS::Neutron::Net
    properties:
      name:
        str_replace:
          template: base_rand_network
          params:
            base: { get_param: base_string }
            rand: { get_resource: random-str }
...

As it stands right now, if I call the master template in horizon, it won't ask for parameter input for parameters that exist only in the sub-templates (such as network_ID in the above example), only the ones that are explicitly defined in the master. I could just go and declare all parameters across all templates in the master, but that is inelegant and kind of defeats the purpose of the modularity I am trying to achieve.

Is what I am asking for possible, or does this functionality not exist yet?