Is there a way to set project metadata in GCP deployment manager












0














We are using GCP Deployment manager for our infrastructure release. We need to have a shared place that could be accessible from all groups(e.g. project metadata). I think it should be great if we could have it as a part of our infrastructure as code, so we could connect it with all the groups.

I think that for now there is no such resource in GCP deployment manager, but I also would not like to have some separate script that will do this update out of the pattern.

Can someone help with this? what is the best way to store common metadata in the cloud, and if the cloud could not provide the right tool, how can we solve this issue in a clear/nice way?










share|improve this question



























    0














    We are using GCP Deployment manager for our infrastructure release. We need to have a shared place that could be accessible from all groups(e.g. project metadata). I think it should be great if we could have it as a part of our infrastructure as code, so we could connect it with all the groups.

    I think that for now there is no such resource in GCP deployment manager, but I also would not like to have some separate script that will do this update out of the pattern.

    Can someone help with this? what is the best way to store common metadata in the cloud, and if the cloud could not provide the right tool, how can we solve this issue in a clear/nice way?










    share|improve this question

























      0












      0








      0


      1





      We are using GCP Deployment manager for our infrastructure release. We need to have a shared place that could be accessible from all groups(e.g. project metadata). I think it should be great if we could have it as a part of our infrastructure as code, so we could connect it with all the groups.

      I think that for now there is no such resource in GCP deployment manager, but I also would not like to have some separate script that will do this update out of the pattern.

      Can someone help with this? what is the best way to store common metadata in the cloud, and if the cloud could not provide the right tool, how can we solve this issue in a clear/nice way?










      share|improve this question













      We are using GCP Deployment manager for our infrastructure release. We need to have a shared place that could be accessible from all groups(e.g. project metadata). I think it should be great if we could have it as a part of our infrastructure as code, so we could connect it with all the groups.

      I think that for now there is no such resource in GCP deployment manager, but I also would not like to have some separate script that will do this update out of the pattern.

      Can someone help with this? what is the best way to store common metadata in the cloud, and if the cloud could not provide the right tool, how can we solve this issue in a clear/nice way?







      google-cloud-platform google-deployment-manager






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 19 '18 at 13:50









      Rafik Avtoyan

      817




      817
























          2 Answers
          2






          active

          oldest

          votes


















          1














          Setting project wide metadata is done using the compute.v1.projects API which is not supported for DM. You can view a list of the supported resources for DM here.
          You may want to suggest support for this resource through a Feature Request






          share|improve this answer





























            0














            Here is a yaml config file and its template for you:



            The project.yaml configuration :



            # Set project metadata

            imports:
            - path: project.jinja

            resources:
            - name: project
            type: project.jinja
            properties:
            key: 'abcd'
            value: 1234


            And the project.jinja template:



            {#
            Template: Set Project Metadata
            #}

            resources:
            - name: data
            action: gcp-types/compute-v1:compute.projects.setCommonInstanceMetadata
            metadata:
            runtimePolicy:
            - UPDATE_ON_CHANGE
            properties:
            items:
            - key: {{ properties["key"] }}
            value: {{ properties["value"] }}





            share|improve this answer





















            • Please refer to How do I write a good answer and provide some details in your answer.
              – Tom M
              Dec 3 '18 at 17:27










            • No, I will not.
              – Olivier Adam
              Dec 4 '18 at 9:23













            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%2f53376076%2fis-there-a-way-to-set-project-metadata-in-gcp-deployment-manager%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            1














            Setting project wide metadata is done using the compute.v1.projects API which is not supported for DM. You can view a list of the supported resources for DM here.
            You may want to suggest support for this resource through a Feature Request






            share|improve this answer


























              1














              Setting project wide metadata is done using the compute.v1.projects API which is not supported for DM. You can view a list of the supported resources for DM here.
              You may want to suggest support for this resource through a Feature Request






              share|improve this answer
























                1












                1








                1






                Setting project wide metadata is done using the compute.v1.projects API which is not supported for DM. You can view a list of the supported resources for DM here.
                You may want to suggest support for this resource through a Feature Request






                share|improve this answer












                Setting project wide metadata is done using the compute.v1.projects API which is not supported for DM. You can view a list of the supported resources for DM here.
                You may want to suggest support for this resource through a Feature Request







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 20 '18 at 18:46









                Patrick W

                8381110




                8381110

























                    0














                    Here is a yaml config file and its template for you:



                    The project.yaml configuration :



                    # Set project metadata

                    imports:
                    - path: project.jinja

                    resources:
                    - name: project
                    type: project.jinja
                    properties:
                    key: 'abcd'
                    value: 1234


                    And the project.jinja template:



                    {#
                    Template: Set Project Metadata
                    #}

                    resources:
                    - name: data
                    action: gcp-types/compute-v1:compute.projects.setCommonInstanceMetadata
                    metadata:
                    runtimePolicy:
                    - UPDATE_ON_CHANGE
                    properties:
                    items:
                    - key: {{ properties["key"] }}
                    value: {{ properties["value"] }}





                    share|improve this answer





















                    • Please refer to How do I write a good answer and provide some details in your answer.
                      – Tom M
                      Dec 3 '18 at 17:27










                    • No, I will not.
                      – Olivier Adam
                      Dec 4 '18 at 9:23


















                    0














                    Here is a yaml config file and its template for you:



                    The project.yaml configuration :



                    # Set project metadata

                    imports:
                    - path: project.jinja

                    resources:
                    - name: project
                    type: project.jinja
                    properties:
                    key: 'abcd'
                    value: 1234


                    And the project.jinja template:



                    {#
                    Template: Set Project Metadata
                    #}

                    resources:
                    - name: data
                    action: gcp-types/compute-v1:compute.projects.setCommonInstanceMetadata
                    metadata:
                    runtimePolicy:
                    - UPDATE_ON_CHANGE
                    properties:
                    items:
                    - key: {{ properties["key"] }}
                    value: {{ properties["value"] }}





                    share|improve this answer





















                    • Please refer to How do I write a good answer and provide some details in your answer.
                      – Tom M
                      Dec 3 '18 at 17:27










                    • No, I will not.
                      – Olivier Adam
                      Dec 4 '18 at 9:23
















                    0












                    0








                    0






                    Here is a yaml config file and its template for you:



                    The project.yaml configuration :



                    # Set project metadata

                    imports:
                    - path: project.jinja

                    resources:
                    - name: project
                    type: project.jinja
                    properties:
                    key: 'abcd'
                    value: 1234


                    And the project.jinja template:



                    {#
                    Template: Set Project Metadata
                    #}

                    resources:
                    - name: data
                    action: gcp-types/compute-v1:compute.projects.setCommonInstanceMetadata
                    metadata:
                    runtimePolicy:
                    - UPDATE_ON_CHANGE
                    properties:
                    items:
                    - key: {{ properties["key"] }}
                    value: {{ properties["value"] }}





                    share|improve this answer












                    Here is a yaml config file and its template for you:



                    The project.yaml configuration :



                    # Set project metadata

                    imports:
                    - path: project.jinja

                    resources:
                    - name: project
                    type: project.jinja
                    properties:
                    key: 'abcd'
                    value: 1234


                    And the project.jinja template:



                    {#
                    Template: Set Project Metadata
                    #}

                    resources:
                    - name: data
                    action: gcp-types/compute-v1:compute.projects.setCommonInstanceMetadata
                    metadata:
                    runtimePolicy:
                    - UPDATE_ON_CHANGE
                    properties:
                    items:
                    - key: {{ properties["key"] }}
                    value: {{ properties["value"] }}






                    share|improve this answer












                    share|improve this answer



                    share|improve this answer










                    answered Dec 3 '18 at 17:05









                    Olivier Adam

                    1




                    1












                    • Please refer to How do I write a good answer and provide some details in your answer.
                      – Tom M
                      Dec 3 '18 at 17:27










                    • No, I will not.
                      – Olivier Adam
                      Dec 4 '18 at 9:23




















                    • Please refer to How do I write a good answer and provide some details in your answer.
                      – Tom M
                      Dec 3 '18 at 17:27










                    • No, I will not.
                      – Olivier Adam
                      Dec 4 '18 at 9:23


















                    Please refer to How do I write a good answer and provide some details in your answer.
                    – Tom M
                    Dec 3 '18 at 17:27




                    Please refer to How do I write a good answer and provide some details in your answer.
                    – Tom M
                    Dec 3 '18 at 17:27












                    No, I will not.
                    – Olivier Adam
                    Dec 4 '18 at 9:23






                    No, I will not.
                    – Olivier Adam
                    Dec 4 '18 at 9:23




















                    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%2f53376076%2fis-there-a-way-to-set-project-metadata-in-gcp-deployment-manager%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

                    MongoDB - Not Authorized To Execute Command

                    How to fix TextFormField cause rebuild widget in Flutter

                    in spring boot 2.1 many test slices are not allowed anymore due to multiple @BootstrapWith