Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom Extension/Bundle Doesn't Show in Deployments #289

Open
shawn-orange opened this issue Apr 1, 2021 · 2 comments
Open

Custom Extension/Bundle Doesn't Show in Deployments #289

shawn-orange opened this issue Apr 1, 2021 · 2 comments
Labels
Known issue Known issue that is well documented question Further information is requested

Comments

@shawn-orange
Copy link

Question

Provider 0.1.0 is a great improvement, thank you! One of our biggest issues with the beta was that it was missing custom extensions, so it would remove our synonym bundle every time we pushed a change through Terraform. The new version fixes that, and it seems to be working very well.

However, I noticed an oddity - the state of the deployment shown in the GUI doesn't match the actual cluster.

  • Deployment already had custom extension installed - editing the deployment in the GUI, I saw "Settings and Plugins (1)" and clicking into that I saw our custom extension selected.
  • I added the extension block to the terraform file and applied the change.
  • The resulting Activity entry said "Remove xxxxx user bundle", but the synonyms still seem to be there and our index that requires them didn't go red, so I'm confidant that the bundle is installed.
  • When looking at Deployments under the GUI now, I see "Settings and Plugins (0)", when it should say "(1)", and clicking into there, the custom extension is no longer checked.

It's mostly a cosmetic issue, but it would be nice to be able to see the cluster's complete state from the GUI, including the custom extension. Is this something that can be fixed?

@shawn-orange shawn-orange added Team:Delivery question Further information is requested labels Apr 1, 2021
@marclop
Copy link
Contributor

marclop commented Apr 1, 2021

This is a known issue and already reported for other fields in #214.

@tacitus
Copy link

tacitus commented May 30, 2021

I have experienced the same issue when adding Custom Plugins, somehow the provider seems to add the plugin reference at the incorrect node: [Correction: this seems to be a valid configuration for all topologies as per this comment]

{
  ...
  },
  "resources": {
    "elasticsearch": [
      {
        "region": "azure-australiaeast",
        "ref_id": "main-elasticsearch",
        "plan": {
          "tiebreaker_topology": {
            "memory_per_node": 1024
          },
          "cluster_topology": [
  ...
          ],
          "elasticsearch": {
            "version": "7.12.1",
            "user_plugins": [
              {
                "name": "pinyin-analysis",
                "url": "repo://4228934933",
                "elasticsearch_version": "7.12.1"
              }
            ]
          },
          "deployment_template": {
            "id": "azure-io-optimized-v2"
          },
          "autoscaling_enabled": false,
          "transient": {
            "strategy": {
              "autodetect": {}
            }
          }
        }
      }
    ],
    "kibana": [],
    "apm": [],
    "enterprise_search": []
  }

It should be added within each cluster_topology node:

 {
...
 "resources": {
   "elasticsearch": [
     {
       "region": "gcp-us-west1",
       "ref_id": "main-elasticsearch",
       "plan": {
         "tiebreaker_topology": {
           "memory_per_node": 1024
         },
         "cluster_topology": [
           {
             "id": "coordinating",
             "node_roles": [
               "ingest",
               "remote_cluster_client"
             ],
             "zone_count": 2,
             "elasticsearch": {
               "system_settings": {
                 "scripting": {
                   "stored": {
                     "enabled": true
                   },
                   "inline": {
                     "enabled": true
                   }
                 },
                 "http": {
                   "compression": true,
                   "cors_enabled": false,
                   "cors_max_age": 1728000,
                   "cors_allow_credentials": false
                 },
                 "reindex_whitelist": [],
                 "use_disk_threshold": true,
                 "auto_create_index": true,
                 "enable_close_index": true,
                 "destructive_requires_name": false,
                 "monitoring_collection_interval": -1,
                 "monitoring_history_duration": "3d"
               },
               "enabled_built_in_plugins": [
                 "analysis-nori"
               ],
               "user_bundles": [
                 {
                   "name": "syn1",
                   "url": "repo://3115391005",
                   "elasticsearch_version": "7.*"
                 }
               ]
             },
             "instance_configuration_id": "gcp.coordinating.1",
             "size": {
               "value": 0,
               "resource": "memory"
             }
           },
...
         ],
         "elasticsearch": {
           "version": "7.12.1"
         },

     ...
}

@marclop marclop added the Known issue Known issue that is well documented label Jul 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Known issue Known issue that is well documented question Further information is requested
Projects
None yet
Development

No branches or pull requests

4 participants