make a resource schema dependant on another variable












1














I'm creating a plugin in terraform and say i want to add a schema which can be called only when another schema has be provided.



"host_name": &schema.Schema{
Type: schema.TypeString,
Optional: true,
DefaultFunc: schema.EnvDefaultFunc("host_name", nil),
Description: "Should give name in FQDN if being used for DNS puposes .",
},
"enableDns": &schema.Schema{
Type: schema.TypeString,
Required: true,
DefaultFunc: schema.EnvDefaultFunc("host_name", nil),
Description: "Should give name in FQDN if being used for DNS puposes .",


so here i want to pass the enableDNs String in the .tf file only when host_name is passed ,if it is not given and i pass enableDNs it should throw an error, can anybody point me out on how to do it










share|improve this question





























    1














    I'm creating a plugin in terraform and say i want to add a schema which can be called only when another schema has be provided.



    "host_name": &schema.Schema{
    Type: schema.TypeString,
    Optional: true,
    DefaultFunc: schema.EnvDefaultFunc("host_name", nil),
    Description: "Should give name in FQDN if being used for DNS puposes .",
    },
    "enableDns": &schema.Schema{
    Type: schema.TypeString,
    Required: true,
    DefaultFunc: schema.EnvDefaultFunc("host_name", nil),
    Description: "Should give name in FQDN if being used for DNS puposes .",


    so here i want to pass the enableDNs String in the .tf file only when host_name is passed ,if it is not given and i pass enableDNs it should throw an error, can anybody point me out on how to do it










    share|improve this question



























      1












      1








      1







      I'm creating a plugin in terraform and say i want to add a schema which can be called only when another schema has be provided.



      "host_name": &schema.Schema{
      Type: schema.TypeString,
      Optional: true,
      DefaultFunc: schema.EnvDefaultFunc("host_name", nil),
      Description: "Should give name in FQDN if being used for DNS puposes .",
      },
      "enableDns": &schema.Schema{
      Type: schema.TypeString,
      Required: true,
      DefaultFunc: schema.EnvDefaultFunc("host_name", nil),
      Description: "Should give name in FQDN if being used for DNS puposes .",


      so here i want to pass the enableDNs String in the .tf file only when host_name is passed ,if it is not given and i pass enableDNs it should throw an error, can anybody point me out on how to do it










      share|improve this question















      I'm creating a plugin in terraform and say i want to add a schema which can be called only when another schema has be provided.



      "host_name": &schema.Schema{
      Type: schema.TypeString,
      Optional: true,
      DefaultFunc: schema.EnvDefaultFunc("host_name", nil),
      Description: "Should give name in FQDN if being used for DNS puposes .",
      },
      "enableDns": &schema.Schema{
      Type: schema.TypeString,
      Required: true,
      DefaultFunc: schema.EnvDefaultFunc("host_name", nil),
      Description: "Should give name in FQDN if being used for DNS puposes .",


      so here i want to pass the enableDNs String in the .tf file only when host_name is passed ,if it is not given and i pass enableDNs it should throw an error, can anybody point me out on how to do it







      terraform






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Dec 28 '18 at 15:49









      kostix

      30.1k648102




      30.1k648102










      asked Dec 28 '18 at 7:58









      Saiprasanna SastrySaiprasanna Sastry

      93




      93
























          1 Answer
          1






          active

          oldest

          votes


















          0














          Terraform providers don't really have a first class way to do stuff conditionally based on other parameters other than the ConflictsWith attribute.



          There is a hacky way to do some cross parameter stuff using CustomizeDiff but it's only really used in a couple of places where it's really needed.



          Normally the provider would simply validate the individual parameters and if the API that the provider is working against requires cross parameter validation then this is only seen at apply time when the API returns the error.



          For an example of using CustomizeDiff to throw a plan time error when doing cross parameter validation see the aws_elasticache_cluster resource:



              CustomizeDiff: customdiff.Sequence(
          func(diff *schema.ResourceDiff, v interface{}) error {
          // Plan time validation for az_mode
          // InvalidParameterCombination: Must specify at least two cache nodes in order to specify AZ Mode of 'cross-az'.
          if v, ok := diff.GetOk("az_mode"); !ok || v.(string) != elasticache.AZModeCrossAz {
          return nil
          }
          if v, ok := diff.GetOk("num_cache_nodes"); !ok || v.(int) != 1 {
          return nil
          }
          return errors.New(`az_mode "cross-az" is not supported with num_cache_nodes = 1`)
          },





          share|improve this answer























            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53955348%2fmake-a-resource-schema-dependant-on-another-variable%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            Terraform providers don't really have a first class way to do stuff conditionally based on other parameters other than the ConflictsWith attribute.



            There is a hacky way to do some cross parameter stuff using CustomizeDiff but it's only really used in a couple of places where it's really needed.



            Normally the provider would simply validate the individual parameters and if the API that the provider is working against requires cross parameter validation then this is only seen at apply time when the API returns the error.



            For an example of using CustomizeDiff to throw a plan time error when doing cross parameter validation see the aws_elasticache_cluster resource:



                CustomizeDiff: customdiff.Sequence(
            func(diff *schema.ResourceDiff, v interface{}) error {
            // Plan time validation for az_mode
            // InvalidParameterCombination: Must specify at least two cache nodes in order to specify AZ Mode of 'cross-az'.
            if v, ok := diff.GetOk("az_mode"); !ok || v.(string) != elasticache.AZModeCrossAz {
            return nil
            }
            if v, ok := diff.GetOk("num_cache_nodes"); !ok || v.(int) != 1 {
            return nil
            }
            return errors.New(`az_mode "cross-az" is not supported with num_cache_nodes = 1`)
            },





            share|improve this answer




























              0














              Terraform providers don't really have a first class way to do stuff conditionally based on other parameters other than the ConflictsWith attribute.



              There is a hacky way to do some cross parameter stuff using CustomizeDiff but it's only really used in a couple of places where it's really needed.



              Normally the provider would simply validate the individual parameters and if the API that the provider is working against requires cross parameter validation then this is only seen at apply time when the API returns the error.



              For an example of using CustomizeDiff to throw a plan time error when doing cross parameter validation see the aws_elasticache_cluster resource:



                  CustomizeDiff: customdiff.Sequence(
              func(diff *schema.ResourceDiff, v interface{}) error {
              // Plan time validation for az_mode
              // InvalidParameterCombination: Must specify at least two cache nodes in order to specify AZ Mode of 'cross-az'.
              if v, ok := diff.GetOk("az_mode"); !ok || v.(string) != elasticache.AZModeCrossAz {
              return nil
              }
              if v, ok := diff.GetOk("num_cache_nodes"); !ok || v.(int) != 1 {
              return nil
              }
              return errors.New(`az_mode "cross-az" is not supported with num_cache_nodes = 1`)
              },





              share|improve this answer


























                0












                0








                0






                Terraform providers don't really have a first class way to do stuff conditionally based on other parameters other than the ConflictsWith attribute.



                There is a hacky way to do some cross parameter stuff using CustomizeDiff but it's only really used in a couple of places where it's really needed.



                Normally the provider would simply validate the individual parameters and if the API that the provider is working against requires cross parameter validation then this is only seen at apply time when the API returns the error.



                For an example of using CustomizeDiff to throw a plan time error when doing cross parameter validation see the aws_elasticache_cluster resource:



                    CustomizeDiff: customdiff.Sequence(
                func(diff *schema.ResourceDiff, v interface{}) error {
                // Plan time validation for az_mode
                // InvalidParameterCombination: Must specify at least two cache nodes in order to specify AZ Mode of 'cross-az'.
                if v, ok := diff.GetOk("az_mode"); !ok || v.(string) != elasticache.AZModeCrossAz {
                return nil
                }
                if v, ok := diff.GetOk("num_cache_nodes"); !ok || v.(int) != 1 {
                return nil
                }
                return errors.New(`az_mode "cross-az" is not supported with num_cache_nodes = 1`)
                },





                share|improve this answer














                Terraform providers don't really have a first class way to do stuff conditionally based on other parameters other than the ConflictsWith attribute.



                There is a hacky way to do some cross parameter stuff using CustomizeDiff but it's only really used in a couple of places where it's really needed.



                Normally the provider would simply validate the individual parameters and if the API that the provider is working against requires cross parameter validation then this is only seen at apply time when the API returns the error.



                For an example of using CustomizeDiff to throw a plan time error when doing cross parameter validation see the aws_elasticache_cluster resource:



                    CustomizeDiff: customdiff.Sequence(
                func(diff *schema.ResourceDiff, v interface{}) error {
                // Plan time validation for az_mode
                // InvalidParameterCombination: Must specify at least two cache nodes in order to specify AZ Mode of 'cross-az'.
                if v, ok := diff.GetOk("az_mode"); !ok || v.(string) != elasticache.AZModeCrossAz {
                return nil
                }
                if v, ok := diff.GetOk("num_cache_nodes"); !ok || v.(int) != 1 {
                return nil
                }
                return errors.New(`az_mode "cross-az" is not supported with num_cache_nodes = 1`)
                },






                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Dec 28 '18 at 12:51

























                answered Dec 28 '18 at 12:42









                ydaetskcoRydaetskcoR

                21.2k45373




                21.2k45373






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53955348%2fmake-a-resource-schema-dependant-on-another-variable%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Monofisismo

                    Angular Downloading a file using contenturl with Basic Authentication

                    Olmecas